8 Sep
2005
8 Sep
'05
12:56 p.m.
On 08-09-2005 13:48, Iqbal wrote:
Hi Jan
That explains it, but when I debug the quintum logs, it seems to show that it i processing both the routes, and all message exchanges prior to that have been correct. This is giving the symptom of a 10-15 sec call and then a hangup
That's because the ACK does not get through and the remote party assumes that the caller is dead and terminates the call. This is correct behavior.
And regarding missing Route header field, if the device does not send it then the only thing that you can do is contact the vendor and ask him to fix it.
Jan.