It looks like sipXbridge hates something in the SDP. Take a DEBUG level
log and check what happens within the area when 183 is received.
On 11/26/2012 03:44 PM, Kemal Eroğlu wrote:
Here is the call flow, I hope it helps. Bridge throws an exception
just before the CANCEL is sent from sipxbridge. (172.16.1.26)
Best Regards,
On 23 November 2012 18:00, Tony Graziano <tgrazi...@myitdepartment.net
<mailto:tgrazi...@myitdepartment.net>> wrote:
It is a requirement of the offer-answer model that re-invite with
no SDP attribute return an offer. This offer can be the same as
the original offer but it is a protocol error to return OK with no
SDP body.
It is likely If you dig a packet capture or siptrace out you will
see this. It would help a lot if you explained the call flow and
UA's involved. This most likely occurs during hold or transfer.
On Nov 23, 2012 4:51 AM, "Kemal Eroğlu" <k.erogl...@gmail.com
<mailto:k.erogl...@gmail.com>> wrote:
Hello,
Recently I got an issue about sipxbridge and media relay in
release-4.4. I did some analysis, but stucked at some point.
To summarize the problem,
sipxbridge is ending some trunk calls with a BYE message that
contains:
"sipxbridge;cause=204;text=Unexpected exception processing
response"
(Calls are ended during call setup, generally before sending
"Trying" to the INVITE we received.)
In sipxbridge log, the exception is:
RtpTransmitterEndpoint:"Unexpected exception "
org.sipfoundry.sipxrelay.SymmitronException: Error in
processing request Attempt to set transmitter but Receiver not
set.
Actually the exception occurs in media relay:
sipxrelay:"Exception setting destination "
java.lang.IllegalStateException: Attempt to set transmitter
but Receiver not set.
After analyzing the logs, I saw that, while RTP session
(bridge, symmitrons, session) is being constructed in relay,
somehow the corresponding client transaction is terminated by
bridge. This triggers relay to delete the resources
constructed so far. And then, relay tries to achieve one of
the deleted sources. (It attempts to set the transmitter of a
sym, but it is deleted) That gives the exception and the call
is finished by a BYE from sipxbridge.
I could not find why the transaction is terminated, but in
sipXbridge log, this line is the initial point:
Timer-1:00000000:SipListenerImpl:"Transaction terminated event"
Do you have any idea about this?
Best Regards,
--
Kemal EROĞLU
Karel Electronics R&D Center
Cyberpark, Bilkent 06800 Ankara
+903122650290/3234
_______________________________________________
sipx-dev mailing list
sipx-dev@list.sipfoundry.org <mailto:sipx-dev@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426 <tel:434.984.8426>
sip: helpd...@voice.myitdepartment.net
<mailto:helpd...@voice.myitdepartment.net>
Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net
_______________________________________________
sipx-dev mailing list
sipx-dev@list.sipfoundry.org <mailto:sipx-dev@list.sipfoundry.org>
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
--
Kemal EROĞLU
Karel Electronics R&D Center
Cyberpark, Bilkent 06800 Ankara
+903122650290/3234
_______________________________________________
sipx-dev mailing list
sipx-dev@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
_______________________________________________
sipx-dev mailing list
sipx-dev@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-dev/
