From: Layya H. <lay...@tu...> - 2006-12-28 12:22:17
|
Dear Seagull Users, Hello, I have a question regarding the following note that was posted on the =20 seagull sip-documenation website: ----------------------------------------------------------------------------= ----------------- Miscellaneous considerations Users must be aware of the fact that Seagull currently works only with =20 "perfect" SIP scenarios. It means that the following messages are not =20 properly handled: * Retransmissions * INFO and NOTIFY messages * Optional responses These points are currently in progress. ----------------------------------------------------------------------------= ----------------- For instance, will this simple sip scenario below work? Only messages =20 (2) and (3) have been added to the original scenario. client=09=09server |(1) INVITE | |--------------------->| |(2) 402 Payment Required |<--------------------- |(3) INVITE + payment assertion as an xml text in the sip-message body |--------------------->| |(4) 180 Ringing | |<---------------------| |(5) 200 OK | |<---------------------| |(6) ACK | |--------------------->| | | |(7) PAUSE | | | |(8) BYE | |--------------------->| |(9) 200 OK | |<---------------------| the 2nd INVITE message(3) will now have a CSeq: 2 INVITE and will have this content-type header: Content-Type: multipart/mixed; boundary=3Dboundary1 and the body is as follows: <![CDATA[ --boundary1 Content-Type: application/sdp =09 v=3D0 o=3Duser1 53655765 2353687637 IN IP4 155.208.221.173 s=3DMbone Audio i=3DDiscussion of Mbone Engineering Issues e=3D...@so... c=3DIN IP4 155.208.221.173 t=3D0 0 m=3Daudio 3456 RTP/AVP 0 =09 a=3Drtpmap:0 PCMU/8000 --boundary1 Content-Type: application/samlassertion+xml Content-ID: samlhere <!-- saml assertion here -->]]> Thank you, Layya |