tree cd303c23c77f20b8aceb2c0bba10fe0b4e20be9a
parent fb7a934cfcafcd8a02969747b8427d87ec4cc305
author Holger Hans Peter Freyther <zecke@selfish.org> 1270626834 +0200
committer Holger Hans Peter Freyther <zecke@selfish.org> 1276604652 +0800

nat: Attempt to make MGCP forwarding more robust

When not being able to allocate the msgb for the forwarded data
there is no point in keeping and preparing the transaction. So
we can move the msg creation a bit up and only do the allocations
after having done the msgb allocation.

When receiving a DLCX we will now delete the endpoint right away. This
means when a BSS does not respond to the DLCX our endpoint will not
be blocked. E.g. this could happen when the MGCP is restarting or
in similiar conditions. When the BSS is not responding we move the
burden up the chain to the CallAgent. We have to still keep track
of the transaction id and the bsc pointer to keep the mgcp forward
routine working.