[SIP Beyond VoIP] In-Dialog Requests
yufei.tao at gmail.com
Tue Jul 15 17:15:39 CEST 2014
Thanks very much for the quick reply! What I want to do is to send and
process in-dialog messages like INFO,
nothing to do with complex call features. So I have been using
Invitation from the core, not even Session from Middleware API.
The in-dialog requests (INFO etc) need to have the same call_id,
to_tag, from_tag as the dialog obviously,
and the BYE request that comes after these requests should have its
cseq updated accordingly.
But since by default PJSIP sip session only handles
*INVITE, BYE, ACK, CANCEL, UPDATE and PRACK messages, *
*it gave me an "500 Unhandled by dialog usages" when it received
in-dialog INFO message. *
*Is there any way to solve this please? Thank you!*
SIP SIMPLE SDK is using PJSIP stack but is not a mere 1-1 wrapper for
low level PJSIP functions.
The SDK has its own capabilities and functions that may map or not
with PJSIP functions.
The documentation is here:
On 15 Jul 2014, at 15:32, Yufei Tao <yufei.tao at gmail.com
*> >* I want to use send and process in-dialog (invitation dialog)
requests using Python SipSimple but got 500 unhandled error from the
SipSimple client that receives the in-dialog request. From the
*> >* http://www.pjsip.org/release/0.5.4/PJSIP-Dev-Guide.pdf
*>* 12.1.5. Application can use base dialog API to create and send
requests inside the dialog
*>* 12.1.6. the invite session handles INVITE, BYE, ACK, CANCEL,
UPDATE and PRACK messages that occurs in a dialog. When application
wants to support or handle other types of messages, it must reigster
itself to the dialog as dialog usage. This will enable the application
to process incomding requests that are "unhandled" by existing
*> >* Obviously this is supported by PJSip. But does this have any
wrapper in Python SipSImple? I had a look at the code but failed to
find it. Any tips or examples?
*> >* Thank you!
*>* SIPBeyondVoIP mailing list
*>* SIPBeyondVoIP at lists.ag-projects.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SIPBeyondVoIP