opensipstack-devel

Re: [OpenSIPStack] SUBSCRIBE and MWI

[Joegen B. <joe...@gm...>]

You can use a PSyncPoint as a member variable of the Process class.

PSyncPoint m_ExitSync;

.
.
.
m_ExitSync.Wait();  // <---  Just signal this anywhere you like in the code.

m_UAC->Terminate();
m_UAS->Terminate();

delete m_UAC;
delete m_UAS;
--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Wednesday, April 22, 2009 8:04 AM
To: "'Joegen Baclor'" <jb...@so...>; 
<ope...@li...>
Subject: Re: [OpenSIPStack] SUBSCRIBE and MWI

> No, I haven't needed to do subscribes with my MWI implementation.
>
> With the new MWI code that joegen put in samples, it there an event that 
> can be used in a WaitForXXX in place of the Sleep that he has - like maybe 
> the two events that fire OnTimerExpire and the client 
> OnIncomingSIPMessage? I know I could do CreateEvent() \ SetEvent() for 
> both but don't want to if I could grab existing ones to wait on - just not 
> sure how it's done.
>
> -Bill
>
> -----Original Message-----
> From: Joegen Baclor [mailto:joe...@gm...]
> Sent: Tuesday, April 21, 2009 3:47 PM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] SUBSCRIBE and MWI
>
> No not yet.  Perhaps Bill and Mathias could help it see the light.
>
> --------------------------------------------------
> From: "Ramu" <con...@gm...>
> Sent: Wednesday, April 22, 2009 1:36 AM
> To: <ope...@li...>
> Subject: [OpenSIPStack] SUBSCRIBE and MWI
>
>> Hi,
>>
>> Does OpenSBC support SUBCRIBE message for MWI notification?
>>
>> Please do let know how can setup SBC to forward SUBSCRIBE message.  We
>> setup SBC in UpperRegistration mode.
>>
>> Thanks,
>> Ramu
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.12.1/2070 - Release Date:
>> 04/20/09 17:56:00
>>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and around Java 
> (TM) technology - register by April 22, and save $200 on the JavaOne (SM) 
> conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.12.1/2070 - Release Date: 04/20/09 
> 17:56:00
> 

Re: [OpenSIPStack] SUBSCRIBE and MWI

[Jamieson, W. W <jam...@RL...>]

No, I haven't needed to do subscribes with my MWI implementation.

With the new MWI code that joegen put in samples, it there an event that can be used in a WaitForXXX in place of the Sleep that he has - like maybe the two events that fire OnTimerExpire and the client OnIncomingSIPMessage? I know I could do CreateEvent() \ SetEvent() for both but don't want to if I could grab existing ones to wait on - just not sure how it's done.

-Bill

-----Original Message-----
From: Joegen Baclor [mailto:joe...@gm...] 
Sent: Tuesday, April 21, 2009 3:47 PM
To: ope...@li...
Subject: Re: [OpenSIPStack] SUBSCRIBE and MWI

No not yet.  Perhaps Bill and Mathias could help it see the light.

--------------------------------------------------
From: "Ramu" <con...@gm...>
Sent: Wednesday, April 22, 2009 1:36 AM
To: <ope...@li...>
Subject: [OpenSIPStack] SUBSCRIBE and MWI

> Hi,
>
> Does OpenSBC support SUBCRIBE message for MWI notification?
>
> Please do let know how can setup SBC to forward SUBSCRIBE message.  We 
> setup SBC in UpperRegistration mode.
>
> Thanks,
> Ramu
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save $200 on 
> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.12.1/2070 - Release Date: 
> 04/20/09 17:56:00
> 

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Re: [OpenSIPStack] SUBSCRIBE and MWI

[Joegen B. <joe...@gm...>]

No not yet.  Perhaps Bill and Mathias could help it see the light.

--------------------------------------------------
From: "Ramu" <con...@gm...>
Sent: Wednesday, April 22, 2009 1:36 AM
To: <ope...@li...>
Subject: [OpenSIPStack] SUBSCRIBE and MWI

> Hi,
>
> Does OpenSBC support SUBCRIBE message for MWI notification?
>
> Please do let know how can setup SBC to forward SUBSCRIBE message.  We 
> setup
> SBC in UpperRegistration mode.
>
> Thanks,
> Ramu
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.12.1/2070 - Release Date: 04/20/09 
> 17:56:00
> 

Re: [OpenSIPStack] MWI Notify

[Joegen B. <joe...@gm...>]

Sorry my bad!  Yes those headers must be in the body.   I'll change the 
sample app when I get the chance.

--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Wednesday, April 22, 2009 3:44 AM
To: <ope...@li...>
Subject: Re: [OpenSIPStack] MWI Notify

> Yeah, I got it working a while ago by moving the msg-status-line to the 
> body. I didn't need the msg-account or msg-summary-line. You were right.
>
> Thanks again,
> -Bill
>
> -----Original Message-----
> From: Matthias Dreißig [mailto:mdr...@gm...]
> Sent: Tuesday, April 21, 2009 11:46 AM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> RFC3842 sample:
>
>        NOTIFY sip:al...@al... SIP/2.0
>        To: <sip:al...@ex...>;tag=78923
>        From: <sip:al...@ex...>;tag=4442
>        Date: Mon, 10 Jul 2000 03:55:07 GMT
>        Call-Id: 13...@al...
>        CSeq: 20 NOTIFY
>        Contact: <sip:al...@vm...>
>        Event: message-summary
>        Subscription-State: active
>        Content-Type: application/simple-message-summary
>        Content-Length: 99
> (body part size = 99)
>        Messages-Waiting: yes
>        Message-Account: sip:al...@vm...
>        Voice-Message: 2/8 (0/2)
>
> Your part
>
>        NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
>        From: 
> <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>        To: sip:3768720@130.97.10.5:5060
>        Via: SIP/2.0/UDP 
> 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>        CSeq: 1 NOTIFY
>        Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
>        Contact: <sip:130.97.35.171:5070>
>        Event: message-summary
>        User-Agent: Sample UA
>        Max-Forwards: 70
>        Messages-Waiting: yes
>        Message-Account: sip:test_account@localhost
>        Voice-Message: 1/1
>        Content-Length: 0
> (empty body part size = 0)
>
> For me this looks not the same. After the content length there comes the 
> body.
>
> And here is the definition of body part
> http://tools.ietf.org/html/rfc3842#section-5.2.
>
> Regards,
> Matthias
>
> Jamieson, William W schrieb:
>> The RFC looks the same as what I get on the wire - at least the way
>> Joegen laid it out with  the message-waiting, etc as Custom Headers.
>> It looks like what the RFC shows for the packet - including that they
>> show a non-zero Content-Length (99 in their example).
>> http://tools.ietf.org/html/rfc3842#section-4.1
>>
>> Maybe I'm not seeing how that a body is defined in the text document I 
>> have from dialogic and from the RFC. They both show a blank line after 
>> the last header and before the three MWI parts (Message-Waiting, etc). 
>> I'll try adding them to the body and see what happens.
>>
>> Thanks,
>> -Bill
>>
>> -----Original Message-----
>> From: Matthias Dreißig [mailto:mdr...@gm...]
>> Sent: Tuesday, April 21, 2009 10:56 AM
>> To: ope...@li...
>> Subject: Re: [OpenSIPStack] MWI Notify
>>
>> Hi Bill,
>>
>> what I can tell you is that the content length describes the length of 
>> the body of the NOTIFY message. And because this NOTIFY doesn't have a 
>> body the content length is 0. When I look at the RFC 3842 the information 
>> Message-Waiting, Message-Account,.. has to be as text in the body of the 
>> NOTIFY message and not as headers in the message 
>> (http://tools.ietf.org/html/rfc3842#section-3.5).
>>
>> There are also sample messages
>> (http://tools.ietf.org/html/rfc3842#section-4).
>>
>> Regards,
>> Matthias
>>
>>
>> Jamieson, William W schrieb:
>>
>>> I have it working somewhat now but I notice on the wire that the 
>>> content-length is zero. It's supposed to be the size of all the custom 
>>> headers from what I can tell from the RFC. Is there a standard way of 
>>> setting this? Also, I'm not getting the notification from 
>>> ClientSession::OnIncomingSIPMessage when the server sends back it's 
>>> status 100 "Trying" packet (see capture below).
>>>
>>> Here's what went on the wire. It shows an Internal Server Error but I'm 
>>> not sure it is from the content length being zero. In the last version 
>>> of the MWI service, I wrote my own SIP commands to do this, I found that 
>>> I had to use Invite to get it to work even though Dialogic Support was 
>>> telling me that they accept Notify and they reminded me that Invite may 
>>> go away since it is not the standard. I just assumed that it was because 
>>> I had written my own SIP commands to do it. I'll keep at this and maybe 
>>> try it against our Cisco CM to see how it behaves.
>>>
>>>
>>>
>>> No.     Time            Source                Destination 
>>> Protocol Info
>>>     488 09:02:49.359600 130.97.35.171         130.97.10.5           SIP 
>>> Request: NOTIFY sip:3768720@130.97.10.5:5060
>>>
>>> Frame 488 (586 bytes on wire, 586 bytes captured) Ethernet II, Src:
>>> Dell_4e:64:f8 (00:21:9b:4e:64:f8), Dst: Cisco_f3:26:45
>>> (00:18:ba:f3:26:45) Internet Protocol, Src: 130.97.35.171
>>> (130.97.35.171), Dst: 130.97.10.5 (130.97.10.5) User Datagram Protocol, 
>>> Src Port: vtsas (5070), Dst Port: sip (5060)
>>>     Source port: vtsas (5070)
>>>     Destination port: sip (5060)
>>>     Length: 552
>>>     Checksum: 0xeb12 [correct]
>>> Session Initiation Protocol
>>>     Request-Line: NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
>>>     Message Header
>>>         From: 
>>> <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>>         To: sip:3768720@130.97.10.5:5060
>>>         Via: SIP/2.0/UDP 
>>> 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>>         CSeq: 1 NOTIFY
>>>         Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
>>>         Contact: <sip:130.97.35.171:5070>
>>>         Event: message-summary
>>>         User-Agent: Sample UA
>>>         Max-Forwards: 70
>>>         Messages-Waiting: yes
>>>         Message-Account: sip:test_account@localhost
>>>         Voice-Message: 1/1
>>>         Content-Length: 0
>>>
>>> No.     Time            Source                Destination 
>>> Protocol Info
>>>     489 09:02:49.374563 130.97.10.5           130.97.35.171         SIP 
>>> Status: 100 Trying
>>>
>>> Frame 489 (399 bytes on wire, 399 bytes captured) Ethernet II, Src:
>>> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
>>> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5
>>> (130.97.10.5),
>>> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: 
>>> ibm-pps (1376), Dst Port: vtsas (5070)
>>>     Source port: ibm-pps (1376)
>>>     Destination port: vtsas (5070)
>>>     Length: 365
>>>     Checksum: 0x2aa2 [correct]
>>> Session Initiation Protocol
>>>     Status-Line: SIP/2.0 100 Trying
>>>     Message Header
>>> 
>>> From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>>         To:sip:3768720@130.97.10.5:5060
>>>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>>>         CSeq:1 NOTIFY
>>>         Server:PBX-IP Media Gateway/2.1
>>>         Via:SIP/2.0/UDP 
>>> 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>>         Content-Length:0
>>>
>>> No.     Time            Source                Destination 
>>> Protocol Info
>>>     490 09:02:49.375037 130.97.10.5           130.97.35.171         SIP 
>>> Status: 500 Internal Server Error
>>>
>>> Frame 490 (443 bytes on wire, 443 bytes captured) Ethernet II, Src:
>>> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
>>> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5
>>> (130.97.10.5),
>>> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: 
>>> ibm-pps (1376), Dst Port: vtsas (5070)
>>>     Source port: ibm-pps (1376)
>>>     Destination port: vtsas (5070)
>>>     Length: 409
>>>     Checksum: 0x8abc [correct]
>>> Session Initiation Protocol
>>>     Status-Line: SIP/2.0 500 Internal Server Error
>>>     Message Header
>>> 
>>> From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>>         To:sip:3768720@130.97.10.5:5060;tag=27313246313536410067E556
>>>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>>>         CSeq:1 NOTIFY
>>>         Server:PBX-IP Media Gateway/2.1
>>>         Via:SIP/2.0/UDP 
>>> 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>>         Content-Length:0
>>>
>>> -----Original Message-----
>>> From: Joegen Baclor [mailto:joe...@gm...]
>>> Sent: Thursday, April 16, 2009 11:11 PM
>>> To: ope...@li...
>>> Subject: Re: [OpenSIPStack] MWI Notify
>>>
>>> Hi Bill,
>>>
>>> Download the latest OpenSIPStack from CVS.   There should now be a
>>> sample/client_server_demo directory.  It contains the skeleton code for 
>>> client and server UA.  I've used unsolicited  MWI notify in the client 
>>> to
>>> better serve your purpose.   Here is the snippet from the Main() 
>>> function.
>>> It basically creates two user-agents bound to 5060 and 5070 respectively 
>>> and
>>> let the client (5070) send MWI notify to the server(5060).   You can get 
>>> the
>>> response in OnIncomingSIPMessage of the client session.  I also pasted 
>>> the
>>> snippet below.   Feel free to submit a tutorial based on your experience
>>> with this code.
>>>
>>> HTH,
>>> Joegen
>>>
>>> -----------------------------
>>>
>>> void Process::Main()
>>> {
>>>   #if WIN32
>>>     SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
>>>   #endif
>>>
>>>   /// Create the server and and bind it to port 5060
>>>   m_UAS = new UA();
>>>   m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
>>>   m_UAS->Initialize();
>>>   m_UAS->StartTransportThreads();
>>>   m_UAS->m_SM = new SessionManager( *m_UAS );
>>>
>>>   /// Create the client and bind it to 5070
>>>   m_UAC = new UA();
>>>   m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
>>>   m_UAC->Initialize();
>>>   m_UAC->StartTransportThreads();
>>>   m_UAC->m_SM = new SessionManager( *m_UAC );
>>>
>>>   OString sesionId = ParserTools::GenGUID();
>>>   ClientSession * session = dynamic_cast<ClientSession 
>>> *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), 
>>> sesionId ));
>>>   SIPURI target( "sip:test_account@localhost:5060" );
>>>   SIPURI localURI( "sip:tes...@op..." );
>>>   Via localVia;
>>>   m_UAC->ConstructVia( target.GetAddress(), localVia,
>>> SIPTransport::UDP );
>>>
>>>   session->SetTargetURI( target );
>>>   session->SetRemoteURI( target );
>>>   session->SetLocalURI( localURI );
>>>   session->SetLocalVia( localVia );
>>>
>>>   /// Create a notify and send a test message to the server UA
>>>   SIPMessage notify;
>>>   if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, 
>>> notify ) )
>>>   {
>>>     Event event( "message-summary" );
>>>     notify.SetEvent( event );
>>>
>>>     /// Add Event specific headers headers
>>>     SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
>>>     SIPHeader messageAccount( "Message-Account", 
>>> "sip:test_account@localhost" );
>>>     SIPHeader voiceMessage( "Voice-Message", "1/1" );
>>>     notify.AddCustomHeader( messagesWaiting );
>>>     notify.AddCustomHeader( messageAccount );
>>>     notify.AddCustomHeader( voiceMessage );
>>>
>>>     session->SendRequest( notify );
>>>   }
>>>
>>>   Sleep( 5000 );
>>>
>>>   m_UAC->Terminate();
>>>   m_UAS->Terminate();
>>>
>>>   delete m_UAC;
>>>   delete m_UAS;
>>> }
>>>
>>>
>>>
>>> void ClientSession::OnIncomingSIPMessage(
>>>   SIPMessageArrival & messageEvent
>>> )
>>> {
>>>   SIPMessage message = messageEvent.GetMessage();
>>>   if( message.IsResponse() )
>>>   {
>>>     LOG( LogInfo(), "Got SIP Reponse" );
>>>   }else
>>>   {
>>>     LOG( LogInfo(), "Got SIP Request" )
>>>     SIPMessage response;
>>>     message.CreateResponse( response, SIPMessage::Code200_Ok );
>>>     SendRequest( response );
>>>   }
>>>   Destroy();
>>> }
>>>
>>>
>>> --------------------------------------------------
>>> From: "Jamieson, William W" <jam...@RL...>
>>> Sent: Friday, April 17, 2009 11:24 AM
>>> To: "'Joegen Baclor'" <jb...@so...>;
>>> <ope...@li...>
>>> Subject: Re: [OpenSIPStack] MWI Notify
>>>
>>>
>>>
>>>> That's great!
>>>>
>>>> Thanks.
>>>>
>>>> -Bill
>>>>
>>>> -----Original Message-----
>>>> From: Joegen Baclor [mailto:joe...@gm...]
>>>> Sent: Thursday, April 16, 2009 6:25 PM
>>>> To: ope...@li...
>>>> Subject: Re: [OpenSIPStack] MWI Notify
>>>>
>>>> Hey Jaimieson,
>>>>
>>>> I'll try to crank up a sample application for MWI as your basis.   It
>>>> quite
>>>> time we put some sample tutorials in opensipstack.  Give it several 
>>>> hours.
>>>>
>>>> Joegen
>>>>
>>>> --------------------------------------------------
>>>> From: "Jamieson, William W" <jam...@RL...>
>>>> Sent: Thursday, April 16, 2009 9:35 PM
>>>> To: <ope...@li...>
>>>> Subject: [OpenSIPStack] MWI Notify
>>>>
>>>>
>>>>
>>>>> I'm really after sending an MWI Notify and I'm using the
>>>>> MWIResource and MWIPackage classes. It's an unsolicited Notify so I
>>>>> can't see why I need a subscription but that's the way the classes
>>>>> were written, I think.
>>>>>
>>>>> For now, I have given up on the two MWI classes. This is what I have:
>>>>>
>>>>> Make a SIPMessage called notify which I fill with all the fields I
>>>>> see defined in RFC 3842 (MWI) ... (code omitted)
>>>>>
>>>>> Make a sessionManager
>>>>>
>>>>> B2BUserAgent ua("MWI");
>>>>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>>>>
>>>>> Make a SIPSession:
>>>>>
>>>>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>>>>> "application/reginfo+xml");    // stole this so not sure what the args
>>>>> are
>>>>> OString sessionId = ParserTools::GenGUID(); SIPSession *session =
>>>>> sessionMgr.CreateClientSession(info, sessionId); // now I have the
>>>>> sessionId for the notify CallId which I add to the notify
>>>>> SIPMessage
>>>>>
>>>>> Send the request
>>>>>
>>>>> sessionMgr.SendRequest(invite);
>>>>>
>>>>> Though it compiles, I know it's not right since I'm not getting
>>>>> anything out on the wire. Am I even close? I thought of using this
>>>>> instead of the call to SendRequest but it doesn't seem right to
>>>>> call an event procedure directly...
>>>>>
>>>>> sessionMgr.OnUnsolicitedNotification(invite);
>>>>>
>>>>> It's very frustrating to work with no samples or docs, it's like
>>>>> trying to reverse engineer the whole thing. Can someone steer me to
>>>>> where I might find these?
>>>>>
>>>>> billjam
>>>>> -------------------------------------------------------------------
>>>>> -
>>>>> -
>>>>> -
>>>>> -------- Stay on top of everything new and different, both inside
>>>>> and around Java (TM) technology - register by April 22, and save
>>>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>>>> 300 plus technical and hands-on sessions. Register today.
>>>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>>>> _______________________________________________
>>>>> opensipstack-devel mailing list
>>>>> ope...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>>>
>>>>>
>>>>
>>>>> No virus found in this incoming message.
>>>>> Checked by AVG - www.avg.com
>>>>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>>>>> 04/15/09 19:52:00
>>>>>
>>>>>
>>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> -
>>>> -------- Stay on top of everything new and different, both inside
>>>> and around Java
>>>> (TM) technology - register by April 22, and save $200 on the JavaOne
>>>> (SM) conference, June 2-5, 2009, San Francisco.
>>>> 300 plus technical and hands-on sessions. Register today.
>>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>>> _______________________________________________
>>>> opensipstack-devel mailing list
>>>> ope...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>>
>>>> --------------------------------------------------------------------
>>>> -
>>>> -
>>>> -------- Stay on top of everything new and different, both inside
>>>> and around Java (TM) technology - register by April 22, and save
>>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>>> 300 plus technical and hands-on sessions. Register today.
>>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>>> _______________________________________________
>>>> opensipstack-devel mailing list
>>>> ope...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>> No virus found in this incoming message.
>>>> Checked by AVG - www.avg.com
>>>> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date:
>>>> 04/16/09 16:38:00
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save $200 on the 
>>> JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save $200 on
>>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>>
>>>
>>
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on the 
>> JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and around Java 
> (TM) technology - register by April 22, and save $200 on the JavaOne (SM) 
> conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.12.1/2070 - Release Date: 04/20/09 
> 17:56:00
> 

Re: [OpenSIPStack] MWI Notify

[Jamieson, W. W <jam...@RL...>]

Yeah, I got it working a while ago by moving the msg-status-line to the body. I didn't need the msg-account or msg-summary-line. You were right.

Thanks again,
-Bill

-----Original Message-----
From: Matthias Dreißig [mailto:mdr...@gm...]
Sent: Tuesday, April 21, 2009 11:46 AM
To: ope...@li...
Subject: Re: [OpenSIPStack] MWI Notify

RFC3842 sample:

        NOTIFY sip:al...@al... SIP/2.0
        To: <sip:al...@ex...>;tag=78923
        From: <sip:al...@ex...>;tag=4442
        Date: Mon, 10 Jul 2000 03:55:07 GMT
        Call-Id: 13...@al...
        CSeq: 20 NOTIFY
        Contact: <sip:al...@vm...>
        Event: message-summary
        Subscription-State: active
        Content-Type: application/simple-message-summary
        Content-Length: 99
(body part size = 99)
        Messages-Waiting: yes
        Message-Account: sip:al...@vm...
        Voice-Message: 2/8 (0/2)

Your part

        NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
        From:  <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
        To: sip:3768720@130.97.10.5:5060
        Via: SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
        CSeq: 1 NOTIFY
        Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
        Contact: <sip:130.97.35.171:5070>
        Event: message-summary
        User-Agent: Sample UA
        Max-Forwards: 70
        Messages-Waiting: yes
        Message-Account: sip:test_account@localhost
        Voice-Message: 1/1
        Content-Length: 0
(empty body part size = 0)

For me this looks not the same. After the content length there comes the body.

And here is the definition of body part
http://tools.ietf.org/html/rfc3842#section-5.2.

Regards,
Matthias

Jamieson, William W schrieb:
> The RFC looks the same as what I get on the wire - at least the way
> Joegen laid it out with  the message-waiting, etc as Custom Headers.
> It looks like what the RFC shows for the packet - including that they
> show a non-zero Content-Length (99 in their example).
> http://tools.ietf.org/html/rfc3842#section-4.1
>
> Maybe I'm not seeing how that a body is defined in the text document I have from dialogic and from the RFC. They both show a blank line after the last header and before the three MWI parts (Message-Waiting, etc). I'll try adding them to the body and see what happens.
>
> Thanks,
> -Bill
>
> -----Original Message-----
> From: Matthias Dreißig [mailto:mdr...@gm...]
> Sent: Tuesday, April 21, 2009 10:56 AM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hi Bill,
>
> what I can tell you is that the content length describes the length of the body of the NOTIFY message. And because this NOTIFY doesn't have a body the content length is 0. When I look at the RFC 3842 the information Message-Waiting, Message-Account,.. has to be as text in the body of the NOTIFY message and not as headers in the message (http://tools.ietf.org/html/rfc3842#section-3.5).
>
> There are also sample messages
> (http://tools.ietf.org/html/rfc3842#section-4).
>
> Regards,
> Matthias
>
>
> Jamieson, William W schrieb:
>
>> I have it working somewhat now but I notice on the wire that the content-length is zero. It's supposed to be the size of all the custom headers from what I can tell from the RFC. Is there a standard way of setting this? Also, I'm not getting the notification from ClientSession::OnIncomingSIPMessage when the server sends back it's status 100 "Trying" packet (see capture below).
>>
>> Here's what went on the wire. It shows an Internal Server Error but I'm not sure it is from the content length being zero. In the last version of the MWI service, I wrote my own SIP commands to do this, I found that I had to use Invite to get it to work even though Dialogic Support was telling me that they accept Notify and they reminded me that Invite may go away since it is not the standard. I just assumed that it was because I had written my own SIP commands to do it. I'll keep at this and maybe try it against our Cisco CM to see how it behaves.
>>
>>
>>
>> No.     Time            Source                Destination           Protocol Info
>>     488 09:02:49.359600 130.97.35.171         130.97.10.5           SIP      Request: NOTIFY sip:3768720@130.97.10.5:5060
>>
>> Frame 488 (586 bytes on wire, 586 bytes captured) Ethernet II, Src:
>> Dell_4e:64:f8 (00:21:9b:4e:64:f8), Dst: Cisco_f3:26:45
>> (00:18:ba:f3:26:45) Internet Protocol, Src: 130.97.35.171
>> (130.97.35.171), Dst: 130.97.10.5 (130.97.10.5) User Datagram Protocol, Src Port: vtsas (5070), Dst Port: sip (5060)
>>     Source port: vtsas (5070)
>>     Destination port: sip (5060)
>>     Length: 552
>>     Checksum: 0xeb12 [correct]
>> Session Initiation Protocol
>>     Request-Line: NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
>>     Message Header
>>         From:  <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>         To: sip:3768720@130.97.10.5:5060
>>         Via: SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>         CSeq: 1 NOTIFY
>>         Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
>>         Contact: <sip:130.97.35.171:5070>
>>         Event: message-summary
>>         User-Agent: Sample UA
>>         Max-Forwards: 70
>>         Messages-Waiting: yes
>>         Message-Account: sip:test_account@localhost
>>         Voice-Message: 1/1
>>         Content-Length: 0
>>
>> No.     Time            Source                Destination           Protocol Info
>>     489 09:02:49.374563 130.97.10.5           130.97.35.171         SIP      Status: 100 Trying
>>
>> Frame 489 (399 bytes on wire, 399 bytes captured) Ethernet II, Src:
>> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
>> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5
>> (130.97.10.5),
>> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>>     Source port: ibm-pps (1376)
>>     Destination port: vtsas (5070)
>>     Length: 365
>>     Checksum: 0x2aa2 [correct]
>> Session Initiation Protocol
>>     Status-Line: SIP/2.0 100 Trying
>>     Message Header
>>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>         To:sip:3768720@130.97.10.5:5060
>>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>>         CSeq:1 NOTIFY
>>         Server:PBX-IP Media Gateway/2.1
>>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>         Content-Length:0
>>
>> No.     Time            Source                Destination           Protocol Info
>>     490 09:02:49.375037 130.97.10.5           130.97.35.171         SIP      Status: 500 Internal Server Error
>>
>> Frame 490 (443 bytes on wire, 443 bytes captured) Ethernet II, Src:
>> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
>> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5
>> (130.97.10.5),
>> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>>     Source port: ibm-pps (1376)
>>     Destination port: vtsas (5070)
>>     Length: 409
>>     Checksum: 0x8abc [correct]
>> Session Initiation Protocol
>>     Status-Line: SIP/2.0 500 Internal Server Error
>>     Message Header
>>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>         To:sip:3768720@130.97.10.5:5060;tag=27313246313536410067E556
>>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>>         CSeq:1 NOTIFY
>>         Server:PBX-IP Media Gateway/2.1
>>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>         Content-Length:0
>>
>> -----Original Message-----
>> From: Joegen Baclor [mailto:joe...@gm...]
>> Sent: Thursday, April 16, 2009 11:11 PM
>> To: ope...@li...
>> Subject: Re: [OpenSIPStack] MWI Notify
>>
>> Hi Bill,
>>
>> Download the latest OpenSIPStack from CVS.   There should now be a
>> sample/client_server_demo directory.  It contains the skeleton code for client and server UA.  I've used unsolicited  MWI notify in the client to
>> better serve your purpose.   Here is the snippet from the Main() function.
>> It basically creates two user-agents bound to 5060 and 5070 respectively and
>> let the client (5070) send MWI notify to the server(5060).   You can get the
>> response in OnIncomingSIPMessage of the client session.  I also pasted the
>> snippet below.   Feel free to submit a tutorial based on your experience
>> with this code.
>>
>> HTH,
>> Joegen
>>
>> -----------------------------
>>
>> void Process::Main()
>> {
>>   #if WIN32
>>     SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
>>   #endif
>>
>>   /// Create the server and and bind it to port 5060
>>   m_UAS = new UA();
>>   m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
>>   m_UAS->Initialize();
>>   m_UAS->StartTransportThreads();
>>   m_UAS->m_SM = new SessionManager( *m_UAS );
>>
>>   /// Create the client and bind it to 5070
>>   m_UAC = new UA();
>>   m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
>>   m_UAC->Initialize();
>>   m_UAC->StartTransportThreads();
>>   m_UAC->m_SM = new SessionManager( *m_UAC );
>>
>>   OString sesionId = ParserTools::GenGUID();
>>   ClientSession * session = dynamic_cast<ClientSession *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), sesionId ));
>>   SIPURI target( "sip:test_account@localhost:5060" );
>>   SIPURI localURI( "sip:tes...@op..." );
>>   Via localVia;
>>   m_UAC->ConstructVia( target.GetAddress(), localVia,
>> SIPTransport::UDP );
>>
>>   session->SetTargetURI( target );
>>   session->SetRemoteURI( target );
>>   session->SetLocalURI( localURI );
>>   session->SetLocalVia( localVia );
>>
>>   /// Create a notify and send a test message to the server UA
>>   SIPMessage notify;
>>   if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, notify ) )
>>   {
>>     Event event( "message-summary" );
>>     notify.SetEvent( event );
>>
>>     /// Add Event specific headers headers
>>     SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
>>     SIPHeader messageAccount( "Message-Account", "sip:test_account@localhost" );
>>     SIPHeader voiceMessage( "Voice-Message", "1/1" );
>>     notify.AddCustomHeader( messagesWaiting );
>>     notify.AddCustomHeader( messageAccount );
>>     notify.AddCustomHeader( voiceMessage );
>>
>>     session->SendRequest( notify );
>>   }
>>
>>   Sleep( 5000 );
>>
>>   m_UAC->Terminate();
>>   m_UAS->Terminate();
>>
>>   delete m_UAC;
>>   delete m_UAS;
>> }
>>
>>
>>
>> void ClientSession::OnIncomingSIPMessage(
>>   SIPMessageArrival & messageEvent
>> )
>> {
>>   SIPMessage message = messageEvent.GetMessage();
>>   if( message.IsResponse() )
>>   {
>>     LOG( LogInfo(), "Got SIP Reponse" );
>>   }else
>>   {
>>     LOG( LogInfo(), "Got SIP Request" )
>>     SIPMessage response;
>>     message.CreateResponse( response, SIPMessage::Code200_Ok );
>>     SendRequest( response );
>>   }
>>   Destroy();
>> }
>>
>>
>> --------------------------------------------------
>> From: "Jamieson, William W" <jam...@RL...>
>> Sent: Friday, April 17, 2009 11:24 AM
>> To: "'Joegen Baclor'" <jb...@so...>;
>> <ope...@li...>
>> Subject: Re: [OpenSIPStack] MWI Notify
>>
>>
>>
>>> That's great!
>>>
>>> Thanks.
>>>
>>> -Bill
>>>
>>> -----Original Message-----
>>> From: Joegen Baclor [mailto:joe...@gm...]
>>> Sent: Thursday, April 16, 2009 6:25 PM
>>> To: ope...@li...
>>> Subject: Re: [OpenSIPStack] MWI Notify
>>>
>>> Hey Jaimieson,
>>>
>>> I'll try to crank up a sample application for MWI as your basis.   It
>>> quite
>>> time we put some sample tutorials in opensipstack.  Give it several hours.
>>>
>>> Joegen
>>>
>>> --------------------------------------------------
>>> From: "Jamieson, William W" <jam...@RL...>
>>> Sent: Thursday, April 16, 2009 9:35 PM
>>> To: <ope...@li...>
>>> Subject: [OpenSIPStack] MWI Notify
>>>
>>>
>>>
>>>> I'm really after sending an MWI Notify and I'm using the
>>>> MWIResource and MWIPackage classes. It's an unsolicited Notify so I
>>>> can't see why I need a subscription but that's the way the classes
>>>> were written, I think.
>>>>
>>>> For now, I have given up on the two MWI classes. This is what I have:
>>>>
>>>> Make a SIPMessage called notify which I fill with all the fields I
>>>> see defined in RFC 3842 (MWI) ... (code omitted)
>>>>
>>>> Make a sessionManager
>>>>
>>>> B2BUserAgent ua("MWI");
>>>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>>>
>>>> Make a SIPSession:
>>>>
>>>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>>>> "application/reginfo+xml");    // stole this so not sure what the args
>>>> are
>>>> OString sessionId = ParserTools::GenGUID(); SIPSession *session =
>>>> sessionMgr.CreateClientSession(info, sessionId); // now I have the
>>>> sessionId for the notify CallId which I add to the notify
>>>> SIPMessage
>>>>
>>>> Send the request
>>>>
>>>> sessionMgr.SendRequest(invite);
>>>>
>>>> Though it compiles, I know it's not right since I'm not getting
>>>> anything out on the wire. Am I even close? I thought of using this
>>>> instead of the call to SendRequest but it doesn't seem right to
>>>> call an event procedure directly...
>>>>
>>>> sessionMgr.OnUnsolicitedNotification(invite);
>>>>
>>>> It's very frustrating to work with no samples or docs, it's like
>>>> trying to reverse engineer the whole thing. Can someone steer me to
>>>> where I might find these?
>>>>
>>>> billjam
>>>> -------------------------------------------------------------------
>>>> -
>>>> -
>>>> -
>>>> -------- Stay on top of everything new and different, both inside
>>>> and around Java (TM) technology - register by April 22, and save
>>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>>> 300 plus technical and hands-on sessions. Register today.
>>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>>> _______________________________________________
>>>> opensipstack-devel mailing list
>>>> ope...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>>
>>>>
>>>
>>>> No virus found in this incoming message.
>>>> Checked by AVG - www.avg.com
>>>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>>>> 04/15/09 19:52:00
>>>>
>>>>
>>>>
>>> --------------------------------------------------------------------
>>> -
>>> -
>>> -------- Stay on top of everything new and different, both inside
>>> and around Java
>>> (TM) technology - register by April 22, and save $200 on the JavaOne
>>> (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>> --------------------------------------------------------------------
>>> -
>>> -
>>> -------- Stay on top of everything new and different, both inside
>>> and around Java (TM) technology - register by April 22, and save
>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>>
>>>
>>
>>
>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date:
>>> 04/16/09 16:38:00
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> -
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>> ---------------------------------------------------------------------
>> -
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>>
>>
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save $200 on
> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Re: [OpenSIPStack] MWI Notify

[Matthias D. <mdr...@gm...>]

RFC3842 sample:

	NOTIFY sip:al...@al... SIP/2.0
	To: <sip:al...@ex...>;tag=78923
	From: <sip:al...@ex...>;tag=4442
	Date: Mon, 10 Jul 2000 03:55:07 GMT
	Call-Id: 13...@al...
	CSeq: 20 NOTIFY
	Contact: <sip:al...@vm...>
	Event: message-summary
	Subscription-State: active
	Content-Type: application/simple-message-summary
	Content-Length: 99
(body part size = 99)
	Messages-Waiting: yes
	Message-Account: sip:al...@vm...
	Voice-Message: 2/8 (0/2)

Your part

        NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
	From:  <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
        To: sip:3768720@130.97.10.5:5060
        Via: SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
        CSeq: 1 NOTIFY
        Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
        Contact: <sip:130.97.35.171:5070>
        Event: message-summary
        User-Agent: Sample UA
        Max-Forwards: 70
        Messages-Waiting: yes
        Message-Account: sip:test_account@localhost
        Voice-Message: 1/1
        Content-Length: 0
(empty body part size = 0)

For me this looks not the same. After the content length there comes the
body.

And here is the definition of body part
http://tools.ietf.org/html/rfc3842#section-5.2.

Regards,
Matthias

Jamieson, William W schrieb:
> The RFC looks the same as what I get on the wire - at least the way Joegen laid it out with  the message-waiting, etc as Custom Headers. It looks like what the RFC shows for the packet - including that they show a non-zero Content-Length (99 in their example). http://tools.ietf.org/html/rfc3842#section-4.1
>
> Maybe I'm not seeing how that a body is defined in the text document I have from dialogic and from the RFC. They both show a blank line after the last header and before the three MWI parts (Message-Waiting, etc). I'll try adding them to the body and see what happens.
>
> Thanks,
> -Bill
>
> -----Original Message-----
> From: Matthias Dreißig [mailto:mdr...@gm...]
> Sent: Tuesday, April 21, 2009 10:56 AM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hi Bill,
>
> what I can tell you is that the content length describes the length of the body of the NOTIFY message. And because this NOTIFY doesn't have a body the content length is 0. When I look at the RFC 3842 the information Message-Waiting, Message-Account,.. has to be as text in the body of the NOTIFY message and not as headers in the message (http://tools.ietf.org/html/rfc3842#section-3.5).
>
> There are also sample messages
> (http://tools.ietf.org/html/rfc3842#section-4).
>
> Regards,
> Matthias
>
>
> Jamieson, William W schrieb:
>   
>> I have it working somewhat now but I notice on the wire that the content-length is zero. It's supposed to be the size of all the custom headers from what I can tell from the RFC. Is there a standard way of setting this? Also, I'm not getting the notification from ClientSession::OnIncomingSIPMessage when the server sends back it's status 100 "Trying" packet (see capture below).
>>
>> Here's what went on the wire. It shows an Internal Server Error but I'm not sure it is from the content length being zero. In the last version of the MWI service, I wrote my own SIP commands to do this, I found that I had to use Invite to get it to work even though Dialogic Support was telling me that they accept Notify and they reminded me that Invite may go away since it is not the standard. I just assumed that it was because I had written my own SIP commands to do it. I'll keep at this and maybe try it against our Cisco CM to see how it behaves.
>>
>>
>>
>> No.     Time            Source                Destination           Protocol Info
>>     488 09:02:49.359600 130.97.35.171         130.97.10.5           SIP      Request: NOTIFY sip:3768720@130.97.10.5:5060
>>
>> Frame 488 (586 bytes on wire, 586 bytes captured) Ethernet II, Src:
>> Dell_4e:64:f8 (00:21:9b:4e:64:f8), Dst: Cisco_f3:26:45
>> (00:18:ba:f3:26:45) Internet Protocol, Src: 130.97.35.171
>> (130.97.35.171), Dst: 130.97.10.5 (130.97.10.5) User Datagram Protocol, Src Port: vtsas (5070), Dst Port: sip (5060)
>>     Source port: vtsas (5070)
>>     Destination port: sip (5060)
>>     Length: 552
>>     Checksum: 0xeb12 [correct]
>> Session Initiation Protocol
>>     Request-Line: NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
>>     Message Header
>>         From:  <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>         To: sip:3768720@130.97.10.5:5060
>>         Via: SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>         CSeq: 1 NOTIFY
>>         Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
>>         Contact: <sip:130.97.35.171:5070>
>>         Event: message-summary
>>         User-Agent: Sample UA
>>         Max-Forwards: 70
>>         Messages-Waiting: yes
>>         Message-Account: sip:test_account@localhost
>>         Voice-Message: 1/1
>>         Content-Length: 0
>>
>> No.     Time            Source                Destination           Protocol Info
>>     489 09:02:49.374563 130.97.10.5           130.97.35.171         SIP      Status: 100 Trying
>>
>> Frame 489 (399 bytes on wire, 399 bytes captured) Ethernet II, Src:
>> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
>> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5 (130.97.10.5),
>> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>>     Source port: ibm-pps (1376)
>>     Destination port: vtsas (5070)
>>     Length: 365
>>     Checksum: 0x2aa2 [correct]
>> Session Initiation Protocol
>>     Status-Line: SIP/2.0 100 Trying
>>     Message Header
>>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>         To:sip:3768720@130.97.10.5:5060
>>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>>         CSeq:1 NOTIFY
>>         Server:PBX-IP Media Gateway/2.1
>>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>         Content-Length:0
>>
>> No.     Time            Source                Destination           Protocol Info
>>     490 09:02:49.375037 130.97.10.5           130.97.35.171         SIP      Status: 500 Internal Server Error
>>
>> Frame 490 (443 bytes on wire, 443 bytes captured) Ethernet II, Src:
>> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
>> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5 (130.97.10.5),
>> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>>     Source port: ibm-pps (1376)
>>     Destination port: vtsas (5070)
>>     Length: 409
>>     Checksum: 0x8abc [correct]
>> Session Initiation Protocol
>>     Status-Line: SIP/2.0 500 Internal Server Error
>>     Message Header
>>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>>         To:sip:3768720@130.97.10.5:5060;tag=27313246313536410067E556
>>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>>         CSeq:1 NOTIFY
>>         Server:PBX-IP Media Gateway/2.1
>>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>>         Content-Length:0
>>
>> -----Original Message-----
>> From: Joegen Baclor [mailto:joe...@gm...]
>> Sent: Thursday, April 16, 2009 11:11 PM
>> To: ope...@li...
>> Subject: Re: [OpenSIPStack] MWI Notify
>>
>> Hi Bill,
>>
>> Download the latest OpenSIPStack from CVS.   There should now be a
>> sample/client_server_demo directory.  It contains the skeleton code for client and server UA.  I've used unsolicited  MWI notify in the client to
>> better serve your purpose.   Here is the snippet from the Main() function.
>> It basically creates two user-agents bound to 5060 and 5070 respectively and
>> let the client (5070) send MWI notify to the server(5060).   You can get the
>> response in OnIncomingSIPMessage of the client session.  I also pasted the
>> snippet below.   Feel free to submit a tutorial based on your experience
>> with this code.
>>
>> HTH,
>> Joegen
>>
>> -----------------------------
>>
>> void Process::Main()
>> {
>>   #if WIN32
>>     SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
>>   #endif
>>
>>   /// Create the server and and bind it to port 5060
>>   m_UAS = new UA();
>>   m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
>>   m_UAS->Initialize();
>>   m_UAS->StartTransportThreads();
>>   m_UAS->m_SM = new SessionManager( *m_UAS );
>>
>>   /// Create the client and bind it to 5070
>>   m_UAC = new UA();
>>   m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
>>   m_UAC->Initialize();
>>   m_UAC->StartTransportThreads();
>>   m_UAC->m_SM = new SessionManager( *m_UAC );
>>
>>   OString sesionId = ParserTools::GenGUID();
>>   ClientSession * session = dynamic_cast<ClientSession *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), sesionId ));
>>   SIPURI target( "sip:test_account@localhost:5060" );
>>   SIPURI localURI( "sip:tes...@op..." );
>>   Via localVia;
>>   m_UAC->ConstructVia( target.GetAddress(), localVia,
>> SIPTransport::UDP );
>>
>>   session->SetTargetURI( target );
>>   session->SetRemoteURI( target );
>>   session->SetLocalURI( localURI );
>>   session->SetLocalVia( localVia );
>>
>>   /// Create a notify and send a test message to the server UA
>>   SIPMessage notify;
>>   if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, notify ) )
>>   {
>>     Event event( "message-summary" );
>>     notify.SetEvent( event );
>>
>>     /// Add Event specific headers headers
>>     SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
>>     SIPHeader messageAccount( "Message-Account", "sip:test_account@localhost" );
>>     SIPHeader voiceMessage( "Voice-Message", "1/1" );
>>     notify.AddCustomHeader( messagesWaiting );
>>     notify.AddCustomHeader( messageAccount );
>>     notify.AddCustomHeader( voiceMessage );
>>
>>     session->SendRequest( notify );
>>   }
>>
>>   Sleep( 5000 );
>>
>>   m_UAC->Terminate();
>>   m_UAS->Terminate();
>>
>>   delete m_UAC;
>>   delete m_UAS;
>> }
>>
>>
>>
>> void ClientSession::OnIncomingSIPMessage(
>>   SIPMessageArrival & messageEvent
>> )
>> {
>>   SIPMessage message = messageEvent.GetMessage();
>>   if( message.IsResponse() )
>>   {
>>     LOG( LogInfo(), "Got SIP Reponse" );
>>   }else
>>   {
>>     LOG( LogInfo(), "Got SIP Request" )
>>     SIPMessage response;
>>     message.CreateResponse( response, SIPMessage::Code200_Ok );
>>     SendRequest( response );
>>   }
>>   Destroy();
>> }
>>
>>
>> --------------------------------------------------
>> From: "Jamieson, William W" <jam...@RL...>
>> Sent: Friday, April 17, 2009 11:24 AM
>> To: "'Joegen Baclor'" <jb...@so...>;
>> <ope...@li...>
>> Subject: Re: [OpenSIPStack] MWI Notify
>>
>>
>>     
>>> That's great!
>>>
>>> Thanks.
>>>
>>> -Bill
>>>
>>> -----Original Message-----
>>> From: Joegen Baclor [mailto:joe...@gm...]
>>> Sent: Thursday, April 16, 2009 6:25 PM
>>> To: ope...@li...
>>> Subject: Re: [OpenSIPStack] MWI Notify
>>>
>>> Hey Jaimieson,
>>>
>>> I'll try to crank up a sample application for MWI as your basis.   It
>>> quite
>>> time we put some sample tutorials in opensipstack.  Give it several hours.
>>>
>>> Joegen
>>>
>>> --------------------------------------------------
>>> From: "Jamieson, William W" <jam...@RL...>
>>> Sent: Thursday, April 16, 2009 9:35 PM
>>> To: <ope...@li...>
>>> Subject: [OpenSIPStack] MWI Notify
>>>
>>>
>>>       
>>>> I'm really after sending an MWI Notify and I'm using the MWIResource
>>>> and MWIPackage classes. It's an unsolicited Notify so I can't see
>>>> why I need a subscription but that's the way the classes were
>>>> written, I think.
>>>>
>>>> For now, I have given up on the two MWI classes. This is what I have:
>>>>
>>>> Make a SIPMessage called notify which I fill with all the fields I
>>>> see defined in RFC 3842 (MWI) ... (code omitted)
>>>>
>>>> Make a sessionManager
>>>>
>>>> B2BUserAgent ua("MWI");
>>>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>>>
>>>> Make a SIPSession:
>>>>
>>>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>>>> "application/reginfo+xml");    // stole this so not sure what the args
>>>> are
>>>> OString sessionId = ParserTools::GenGUID(); SIPSession *session =
>>>> sessionMgr.CreateClientSession(info, sessionId); // now I have the
>>>> sessionId for the notify CallId which I add to the notify SIPMessage
>>>>
>>>> Send the request
>>>>
>>>> sessionMgr.SendRequest(invite);
>>>>
>>>> Though it compiles, I know it's not right since I'm not getting
>>>> anything out on the wire. Am I even close? I thought of using this
>>>> instead of the call to SendRequest but it doesn't seem right to call
>>>> an event procedure directly...
>>>>
>>>> sessionMgr.OnUnsolicitedNotification(invite);
>>>>
>>>> It's very frustrating to work with no samples or docs, it's like
>>>> trying to reverse engineer the whole thing. Can someone steer me to
>>>> where I might find these?
>>>>
>>>> billjam
>>>> --------------------------------------------------------------------
>>>> -
>>>> -
>>>> -------- Stay on top of everything new and different, both inside
>>>> and around Java (TM) technology - register by April 22, and save
>>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>>> 300 plus technical and hands-on sessions. Register today.
>>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>>> _______________________________________________
>>>> opensipstack-devel mailing list
>>>> ope...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>>
>>>>         
>>>       
>>>> No virus found in this incoming message.
>>>> Checked by AVG - www.avg.com
>>>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>>>> 04/15/09 19:52:00
>>>>
>>>>
>>>>         
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Stay on top of everything new and different, both inside and
>>> around Java
>>> (TM) technology - register by April 22, and save $200 on the JavaOne
>>> (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save $200 on
>>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>>
>>>       
>>
>>
>>     
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date:
>>> 04/16/09 16:38:00
>>>
>>>
>>>       
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>>
>>     
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>   

Re: [OpenSIPStack] MWI Notify

[Jamieson, W. W <jam...@RL...>]

The RFC looks the same as what I get on the wire - at least the way Joegen laid it out with the message-waiting, etc as Custom Headers. It looks like what the RFC shows for the packet - including that they show a non-zero Content-Length (99 in their example). http://tools.ietf.org/html/rfc3842#section-4.1

Maybe I'm not seeing how that a body is defined in the text document I have from dialogic and from the RFC. They both show a blank line after the last header and before the three MWI parts (Message-Waiting, etc). I'll try adding them to the body and see what happens.

Thanks,
-Bill

-----Original Message-----
From: Matthias Dreißig [mailto:mdr...@gm...]
Sent: Tuesday, April 21, 2009 10:56 AM
To: ope...@li...
Subject: Re: [OpenSIPStack] MWI Notify

Hi Bill,

what I can tell you is that the content length describes the length of the body of the NOTIFY message. And because this NOTIFY doesn't have a body the content length is 0. When I look at the RFC 3842 the information Message-Waiting, Message-Account,.. has to be as text in the body of the NOTIFY message and not as headers in the message (http://tools.ietf.org/html/rfc3842#section-3.5).

There are also sample messages
(http://tools.ietf.org/html/rfc3842#section-4).

Regards,
Matthias


Jamieson, William W schrieb:
> I have it working somewhat now but I notice on the wire that the content-length is zero. It's supposed to be the size of all the custom headers from what I can tell from the RFC. Is there a standard way of setting this? Also, I'm not getting the notification from ClientSession::OnIncomingSIPMessage when the server sends back it's status 100 "Trying" packet (see capture below).
>
> Here's what went on the wire. It shows an Internal Server Error but I'm not sure it is from the content length being zero. In the last version of the MWI service, I wrote my own SIP commands to do this, I found that I had to use Invite to get it to work even though Dialogic Support was telling me that they accept Notify and they reminded me that Invite may go away since it is not the standard. I just assumed that it was because I had written my own SIP commands to do it. I'll keep at this and maybe try it against our Cisco CM to see how it behaves.
>
>
>
> No.     Time            Source                Destination           Protocol Info
>     488 09:02:49.359600 130.97.35.171         130.97.10.5           SIP      Request: NOTIFY sip:3768720@130.97.10.5:5060
>
> Frame 488 (586 bytes on wire, 586 bytes captured) Ethernet II, Src:
> Dell_4e:64:f8 (00:21:9b:4e:64:f8), Dst: Cisco_f3:26:45
> (00:18:ba:f3:26:45) Internet Protocol, Src: 130.97.35.171
> (130.97.35.171), Dst: 130.97.10.5 (130.97.10.5) User Datagram Protocol, Src Port: vtsas (5070), Dst Port: sip (5060)
>     Source port: vtsas (5070)
>     Destination port: sip (5060)
>     Length: 552
>     Checksum: 0xeb12 [correct]
> Session Initiation Protocol
>     Request-Line: NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
>     Message Header
>         From:  <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>         To: sip:3768720@130.97.10.5:5060
>         Via: SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>         CSeq: 1 NOTIFY
>         Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
>         Contact: <sip:130.97.35.171:5070>
>         Event: message-summary
>         User-Agent: Sample UA
>         Max-Forwards: 70
>         Messages-Waiting: yes
>         Message-Account: sip:test_account@localhost
>         Voice-Message: 1/1
>         Content-Length: 0
>
> No.     Time            Source                Destination           Protocol Info
>     489 09:02:49.374563 130.97.10.5           130.97.35.171         SIP      Status: 100 Trying
>
> Frame 489 (399 bytes on wire, 399 bytes captured) Ethernet II, Src:
> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5 (130.97.10.5),
> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>     Source port: ibm-pps (1376)
>     Destination port: vtsas (5070)
>     Length: 365
>     Checksum: 0x2aa2 [correct]
> Session Initiation Protocol
>     Status-Line: SIP/2.0 100 Trying
>     Message Header
>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>         To:sip:3768720@130.97.10.5:5060
>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>         CSeq:1 NOTIFY
>         Server:PBX-IP Media Gateway/2.1
>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>         Content-Length:0
>
> No.     Time            Source                Destination           Protocol Info
>     490 09:02:49.375037 130.97.10.5           130.97.35.171         SIP      Status: 500 Internal Server Error
>
> Frame 490 (443 bytes on wire, 443 bytes captured) Ethernet II, Src:
> Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8
> (00:21:9b:4e:64:f8) Internet Protocol, Src: 130.97.10.5 (130.97.10.5),
> Dst: 130.97.35.171 (130.97.35.171) User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>     Source port: ibm-pps (1376)
>     Destination port: vtsas (5070)
>     Length: 409
>     Checksum: 0x8abc [correct]
> Session Initiation Protocol
>     Status-Line: SIP/2.0 500 Internal Server Error
>     Message Header
>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>         To:sip:3768720@130.97.10.5:5060;tag=27313246313536410067E556
>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>         CSeq:1 NOTIFY
>         Server:PBX-IP Media Gateway/2.1
>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>         Content-Length:0
>
> -----Original Message-----
> From: Joegen Baclor [mailto:joe...@gm...]
> Sent: Thursday, April 16, 2009 11:11 PM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hi Bill,
>
> Download the latest OpenSIPStack from CVS.   There should now be a
> sample/client_server_demo directory.  It contains the skeleton code for client and server UA.  I've used unsolicited  MWI notify in the client to
> better serve your purpose.   Here is the snippet from the Main() function.
> It basically creates two user-agents bound to 5060 and 5070 respectively and
> let the client (5070) send MWI notify to the server(5060).   You can get the
> response in OnIncomingSIPMessage of the client session.  I also pasted the
> snippet below.   Feel free to submit a tutorial based on your experience
> with this code.
>
> HTH,
> Joegen
>
> -----------------------------
>
> void Process::Main()
> {
>   #if WIN32
>     SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
>   #endif
>
>   /// Create the server and and bind it to port 5060
>   m_UAS = new UA();
>   m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
>   m_UAS->Initialize();
>   m_UAS->StartTransportThreads();
>   m_UAS->m_SM = new SessionManager( *m_UAS );
>
>   /// Create the client and bind it to 5070
>   m_UAC = new UA();
>   m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
>   m_UAC->Initialize();
>   m_UAC->StartTransportThreads();
>   m_UAC->m_SM = new SessionManager( *m_UAC );
>
>   OString sesionId = ParserTools::GenGUID();
>   ClientSession * session = dynamic_cast<ClientSession *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), sesionId ));
>   SIPURI target( "sip:test_account@localhost:5060" );
>   SIPURI localURI( "sip:tes...@op..." );
>   Via localVia;
>   m_UAC->ConstructVia( target.GetAddress(), localVia,
> SIPTransport::UDP );
>
>   session->SetTargetURI( target );
>   session->SetRemoteURI( target );
>   session->SetLocalURI( localURI );
>   session->SetLocalVia( localVia );
>
>   /// Create a notify and send a test message to the server UA
>   SIPMessage notify;
>   if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, notify ) )
>   {
>     Event event( "message-summary" );
>     notify.SetEvent( event );
>
>     /// Add Event specific headers headers
>     SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
>     SIPHeader messageAccount( "Message-Account", "sip:test_account@localhost" );
>     SIPHeader voiceMessage( "Voice-Message", "1/1" );
>     notify.AddCustomHeader( messagesWaiting );
>     notify.AddCustomHeader( messageAccount );
>     notify.AddCustomHeader( voiceMessage );
>
>     session->SendRequest( notify );
>   }
>
>   Sleep( 5000 );
>
>   m_UAC->Terminate();
>   m_UAS->Terminate();
>
>   delete m_UAC;
>   delete m_UAS;
> }
>
>
>
> void ClientSession::OnIncomingSIPMessage(
>   SIPMessageArrival & messageEvent
> )
> {
>   SIPMessage message = messageEvent.GetMessage();
>   if( message.IsResponse() )
>   {
>     LOG( LogInfo(), "Got SIP Reponse" );
>   }else
>   {
>     LOG( LogInfo(), "Got SIP Request" )
>     SIPMessage response;
>     message.CreateResponse( response, SIPMessage::Code200_Ok );
>     SendRequest( response );
>   }
>   Destroy();
> }
>
>
> --------------------------------------------------
> From: "Jamieson, William W" <jam...@RL...>
> Sent: Friday, April 17, 2009 11:24 AM
> To: "'Joegen Baclor'" <jb...@so...>;
> <ope...@li...>
> Subject: Re: [OpenSIPStack] MWI Notify
>
>
>> That's great!
>>
>> Thanks.
>>
>> -Bill
>>
>> -----Original Message-----
>> From: Joegen Baclor [mailto:joe...@gm...]
>> Sent: Thursday, April 16, 2009 6:25 PM
>> To: ope...@li...
>> Subject: Re: [OpenSIPStack] MWI Notify
>>
>> Hey Jaimieson,
>>
>> I'll try to crank up a sample application for MWI as your basis.   It
>> quite
>> time we put some sample tutorials in opensipstack.  Give it several hours.
>>
>> Joegen
>>
>> --------------------------------------------------
>> From: "Jamieson, William W" <jam...@RL...>
>> Sent: Thursday, April 16, 2009 9:35 PM
>> To: <ope...@li...>
>> Subject: [OpenSIPStack] MWI Notify
>>
>>
>>> I'm really after sending an MWI Notify and I'm using the MWIResource
>>> and MWIPackage classes. It's an unsolicited Notify so I can't see
>>> why I need a subscription but that's the way the classes were
>>> written, I think.
>>>
>>> For now, I have given up on the two MWI classes. This is what I have:
>>>
>>> Make a SIPMessage called notify which I fill with all the fields I
>>> see defined in RFC 3842 (MWI) ... (code omitted)
>>>
>>> Make a sessionManager
>>>
>>> B2BUserAgent ua("MWI");
>>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>>
>>> Make a SIPSession:
>>>
>>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>>> "application/reginfo+xml");    // stole this so not sure what the args
>>> are
>>> OString sessionId = ParserTools::GenGUID(); SIPSession *session =
>>> sessionMgr.CreateClientSession(info, sessionId); // now I have the
>>> sessionId for the notify CallId which I add to the notify SIPMessage
>>>
>>> Send the request
>>>
>>> sessionMgr.SendRequest(invite);
>>>
>>> Though it compiles, I know it's not right since I'm not getting
>>> anything out on the wire. Am I even close? I thought of using this
>>> instead of the call to SendRequest but it doesn't seem right to call
>>> an event procedure directly...
>>>
>>> sessionMgr.OnUnsolicitedNotification(invite);
>>>
>>> It's very frustrating to work with no samples or docs, it's like
>>> trying to reverse engineer the whole thing. Can someone steer me to
>>> where I might find these?
>>>
>>> billjam
>>> --------------------------------------------------------------------
>>> -
>>> -
>>> -------- Stay on top of everything new and different, both inside
>>> and around Java (TM) technology - register by April 22, and save
>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>
>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>>> 04/15/09 19:52:00
>>>
>>>
>> ---------------------------------------------------------------------
>> -
>> -------- Stay on top of everything new and different, both inside and
>> around Java
>> (TM) technology - register by April 22, and save $200 on the JavaOne
>> (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>> ---------------------------------------------------------------------
>> -
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>>
>
>
>
>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date:
>> 04/16/09 16:38:00
>>
>>
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save $200 on
> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Re: [OpenSIPStack] MWI Notify

[Matthias D. <mdr...@gm...>]

Hi Bill,

what I can tell you is that the content length describes the length of
the body of the NOTIFY message. And because this NOTIFY doesn't have a
body the content length is 0. When I look at the RFC 3842 the
information Message-Waiting, Message-Account,.. has to be as text in the
body of the NOTIFY message and not as headers in the message
(http://tools.ietf.org/html/rfc3842#section-3.5).

There are also sample messages
(http://tools.ietf.org/html/rfc3842#section-4).

Regards,
Matthias


Jamieson, William W schrieb:
> I have it working somewhat now but I notice on the wire that the content-length is zero. It's supposed to be the size of all the custom headers from what I can tell from the RFC. Is there a standard way of setting this? Also, I'm not getting the notification from ClientSession::OnIncomingSIPMessage when the server sends back it's status 100 "Trying" packet (see capture below).
>
> Here's what went on the wire. It shows an Internal Server Error but I'm not sure it is from the content length being zero. In the last version of the MWI service, I wrote my own SIP commands to do this, I found that I had to use Invite to get it to work even though Dialogic Support was telling me that they accept Notify and they reminded me that Invite may go away since it is not the standard. I just assumed that it was because I had written my own SIP commands to do it. I'll keep at this and maybe try it against our Cisco CM to see how it behaves.
>
>
>
> No.     Time            Source                Destination           Protocol Info
>     488 09:02:49.359600 130.97.35.171         130.97.10.5           SIP      Request: NOTIFY sip:3768720@130.97.10.5:5060
>
> Frame 488 (586 bytes on wire, 586 bytes captured)
> Ethernet II, Src: Dell_4e:64:f8 (00:21:9b:4e:64:f8), Dst: Cisco_f3:26:45 (00:18:ba:f3:26:45)
> Internet Protocol, Src: 130.97.35.171 (130.97.35.171), Dst: 130.97.10.5 (130.97.10.5)
> User Datagram Protocol, Src Port: vtsas (5070), Dst Port: sip (5060)
>     Source port: vtsas (5070)
>     Destination port: sip (5060)
>     Length: 552
>     Checksum: 0xeb12 [correct]
> Session Initiation Protocol
>     Request-Line: NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
>     Message Header
>         From:  <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>         To: sip:3768720@130.97.10.5:5060
>         Via: SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>         CSeq: 1 NOTIFY
>         Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
>         Contact: <sip:130.97.35.171:5070>
>         Event: message-summary
>         User-Agent: Sample UA
>         Max-Forwards: 70
>         Messages-Waiting: yes
>         Message-Account: sip:test_account@localhost
>         Voice-Message: 1/1
>         Content-Length: 0
>
> No.     Time            Source                Destination           Protocol Info
>     489 09:02:49.374563 130.97.10.5           130.97.35.171         SIP      Status: 100 Trying
>
> Frame 489 (399 bytes on wire, 399 bytes captured)
> Ethernet II, Src: Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8 (00:21:9b:4e:64:f8)
> Internet Protocol, Src: 130.97.10.5 (130.97.10.5), Dst: 130.97.35.171 (130.97.35.171)
> User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>     Source port: ibm-pps (1376)
>     Destination port: vtsas (5070)
>     Length: 365
>     Checksum: 0x2aa2 [correct]
> Session Initiation Protocol
>     Status-Line: SIP/2.0 100 Trying
>     Message Header
>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>         To:sip:3768720@130.97.10.5:5060
>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>         CSeq:1 NOTIFY
>         Server:PBX-IP Media Gateway/2.1
>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>         Content-Length:0
>
> No.     Time            Source                Destination           Protocol Info
>     490 09:02:49.375037 130.97.10.5           130.97.35.171         SIP      Status: 500 Internal Server Error
>
> Frame 490 (443 bytes on wire, 443 bytes captured)
> Ethernet II, Src: Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8 (00:21:9b:4e:64:f8)
> Internet Protocol, Src: 130.97.10.5 (130.97.10.5), Dst: 130.97.35.171 (130.97.35.171)
> User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
>     Source port: ibm-pps (1376)
>     Destination port: vtsas (5070)
>     Length: 409
>     Checksum: 0x8abc [correct]
> Session Initiation Protocol
>     Status-Line: SIP/2.0 500 Internal Server Error
>     Message Header
>         From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
>         To:sip:3768720@130.97.10.5:5060;tag=27313246313536410067E556
>         Call-ID:5385369e-3efe-1810-9603-8376cc92421d
>         CSeq:1 NOTIFY
>         Server:PBX-IP Media Gateway/2.1
>         Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
>         Content-Length:0
>
> -----Original Message-----
> From: Joegen Baclor [mailto:joe...@gm...] 
> Sent: Thursday, April 16, 2009 11:11 PM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hi Bill,
>
> Download the latest OpenSIPStack from CVS.   There should now be a 
> sample/client_server_demo directory.  It contains the skeleton code for client and server UA.  I've used unsolicited  MWI notify in the client to 
> better serve your purpose.   Here is the snippet from the Main() function. 
> It basically creates two user-agents bound to 5060 and 5070 respectively and 
> let the client (5070) send MWI notify to the server(5060).   You can get the 
> response in OnIncomingSIPMessage of the client session.  I also pasted the 
> snippet below.   Feel free to submit a tutorial based on your experience 
> with this code.
>
> HTH,
> Joegen
>
> -----------------------------
>
> void Process::Main()
> {
>   #if WIN32
>     SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
>   #endif
>
>   /// Create the server and and bind it to port 5060
>   m_UAS = new UA();
>   m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
>   m_UAS->Initialize();
>   m_UAS->StartTransportThreads();
>   m_UAS->m_SM = new SessionManager( *m_UAS );
>
>   /// Create the client and bind it to 5070
>   m_UAC = new UA();
>   m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
>   m_UAC->Initialize();
>   m_UAC->StartTransportThreads();
>   m_UAC->m_SM = new SessionManager( *m_UAC );
>
>   OString sesionId = ParserTools::GenGUID();
>   ClientSession * session = dynamic_cast<ClientSession *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), sesionId ));
>   SIPURI target( "sip:test_account@localhost:5060" );
>   SIPURI localURI( "sip:tes...@op..." );
>   Via localVia;
>   m_UAC->ConstructVia( target.GetAddress(), localVia, SIPTransport::UDP );
>
>   session->SetTargetURI( target );
>   session->SetRemoteURI( target );
>   session->SetLocalURI( localURI );
>   session->SetLocalVia( localVia );
>
>   /// Create a notify and send a test message to the server UA
>   SIPMessage notify;
>   if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, notify ) )
>   {
>     Event event( "message-summary" );
>     notify.SetEvent( event );
>
>     /// Add Event specific headers headers
>     SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
>     SIPHeader messageAccount( "Message-Account", "sip:test_account@localhost" );
>     SIPHeader voiceMessage( "Voice-Message", "1/1" );
>     notify.AddCustomHeader( messagesWaiting );
>     notify.AddCustomHeader( messageAccount );
>     notify.AddCustomHeader( voiceMessage );
>
>     session->SendRequest( notify );
>   }
>
>   Sleep( 5000 );
>
>   m_UAC->Terminate();
>   m_UAS->Terminate();
>
>   delete m_UAC;
>   delete m_UAS;
> }
>
>
>
> void ClientSession::OnIncomingSIPMessage(
>   SIPMessageArrival & messageEvent
> )
> {
>   SIPMessage message = messageEvent.GetMessage();
>   if( message.IsResponse() )
>   {
>     LOG( LogInfo(), "Got SIP Reponse" );
>   }else
>   {
>     LOG( LogInfo(), "Got SIP Request" )
>     SIPMessage response;
>     message.CreateResponse( response, SIPMessage::Code200_Ok );
>     SendRequest( response );
>   }
>   Destroy();
> }
>
>
> --------------------------------------------------
> From: "Jamieson, William W" <jam...@RL...>
> Sent: Friday, April 17, 2009 11:24 AM
> To: "'Joegen Baclor'" <jb...@so...>; <ope...@li...>
> Subject: Re: [OpenSIPStack] MWI Notify
>
>   
>> That's great!
>>
>> Thanks.
>>
>> -Bill
>>
>> -----Original Message-----
>> From: Joegen Baclor [mailto:joe...@gm...]
>> Sent: Thursday, April 16, 2009 6:25 PM
>> To: ope...@li...
>> Subject: Re: [OpenSIPStack] MWI Notify
>>
>> Hey Jaimieson,
>>
>> I'll try to crank up a sample application for MWI as your basis.   It 
>> quite
>> time we put some sample tutorials in opensipstack.  Give it several hours.
>>
>> Joegen
>>
>> --------------------------------------------------
>> From: "Jamieson, William W" <jam...@RL...>
>> Sent: Thursday, April 16, 2009 9:35 PM
>> To: <ope...@li...>
>> Subject: [OpenSIPStack] MWI Notify
>>
>>     
>>> I'm really after sending an MWI Notify and I'm using the MWIResource 
>>> and MWIPackage classes. It's an unsolicited Notify so I can't see why 
>>> I need a subscription but that's the way the classes were written, I 
>>> think.
>>>
>>> For now, I have given up on the two MWI classes. This is what I have:
>>>
>>> Make a SIPMessage called notify which I fill with all the fields I 
>>> see defined in RFC 3842 (MWI) ... (code omitted)
>>>
>>> Make a sessionManager
>>>
>>> B2BUserAgent ua("MWI");
>>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>>
>>> Make a SIPSession:
>>>
>>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>>> "application/reginfo+xml");    // stole this so not sure what the args 
>>> are
>>> OString sessionId = ParserTools::GenGUID(); SIPSession *session = 
>>> sessionMgr.CreateClientSession(info, sessionId); // now I have the 
>>> sessionId for the notify CallId which I add to the notify SIPMessage
>>>
>>> Send the request
>>>
>>> sessionMgr.SendRequest(invite);
>>>
>>> Though it compiles, I know it's not right since I'm not getting 
>>> anything out on the wire. Am I even close? I thought of using this 
>>> instead of the call to SendRequest but it doesn't seem right to call 
>>> an event procedure directly...
>>>
>>> sessionMgr.OnUnsolicitedNotification(invite);
>>>
>>> It's very frustrating to work with no samples or docs, it's like 
>>> trying to reverse engineer the whole thing. Can someone steer me to 
>>> where I might find these?
>>>
>>> billjam
>>> ---------------------------------------------------------------------
>>> -
>>> -------- Stay on top of everything new and different, both inside and 
>>> around Java (TM) technology - register by April 22, and save $200 on 
>>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p 
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>       
>>
>>     
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>>> 04/15/09 19:52:00
>>>
>>>       
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and 
>> around Java
>> (TM) technology - register by April 22, and save $200 on the JavaOne 
>> (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p 
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and 
>> around Java (TM) technology - register by April 22, and save $200 on 
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p 
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>>     
>
>
>
>   
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date: 
>> 04/16/09 16:38:00
>>
>>     
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>   

[OpenSIPStack] SUBSCRIBE and MWI

[Ramu <con...@gm...>]

Hi,

Does OpenSBC support SUBCRIBE message for MWI notification?

Please do let know how can setup SBC to forward SUBSCRIBE message.  We setup
SBC in UpperRegistration mode.

Thanks,
Ramu

Re: [OpenSIPStack] MWI Notify

[Jamieson, W. W <jam...@RL...>]

I have it working somewhat now but I notice on the wire that the content-length is zero. It's supposed to be the size of all the custom headers from what I can tell from the RFC. Is there a standard way of setting this? Also, I'm not getting the notification from ClientSession::OnIncomingSIPMessage when the server sends back it's status 100 "Trying" packet (see capture below).

Here's what went on the wire. It shows an Internal Server Error but I'm not sure it is from the content length being zero. In the last version of the MWI service, I wrote my own SIP commands to do this, I found that I had to use Invite to get it to work even though Dialogic Support was telling me that they accept Notify and they reminded me that Invite may go away since it is not the standard. I just assumed that it was because I had written my own SIP commands to do it. I'll keep at this and maybe try it against our Cisco CM to see how it behaves.



No.     Time            Source                Destination           Protocol Info
    488 09:02:49.359600 130.97.35.171         130.97.10.5           SIP      Request: NOTIFY sip:3768720@130.97.10.5:5060

Frame 488 (586 bytes on wire, 586 bytes captured)
Ethernet II, Src: Dell_4e:64:f8 (00:21:9b:4e:64:f8), Dst: Cisco_f3:26:45 (00:18:ba:f3:26:45)
Internet Protocol, Src: 130.97.35.171 (130.97.35.171), Dst: 130.97.10.5 (130.97.10.5)
User Datagram Protocol, Src Port: vtsas (5070), Dst Port: sip (5060)
    Source port: vtsas (5070)
    Destination port: sip (5060)
    Length: 552
    Checksum: 0xeb12 [correct]
Session Initiation Protocol
    Request-Line: NOTIFY sip:3768720@130.97.10.5:5060 SIP/2.0
    Message Header
        From:  <sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
        To: sip:3768720@130.97.10.5:5060
        Via: SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
        CSeq: 1 NOTIFY
        Call-ID: 5385369e-3efe-1810-9603-8376cc92421d
        Contact: <sip:130.97.35.171:5070>
        Event: message-summary
        User-Agent: Sample UA
        Max-Forwards: 70
        Messages-Waiting: yes
        Message-Account: sip:test_account@localhost
        Voice-Message: 1/1
        Content-Length: 0

No.     Time            Source                Destination           Protocol Info
    489 09:02:49.374563 130.97.10.5           130.97.35.171         SIP      Status: 100 Trying

Frame 489 (399 bytes on wire, 399 bytes captured)
Ethernet II, Src: Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8 (00:21:9b:4e:64:f8)
Internet Protocol, Src: 130.97.10.5 (130.97.10.5), Dst: 130.97.35.171 (130.97.35.171)
User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
    Source port: ibm-pps (1376)
    Destination port: vtsas (5070)
    Length: 365
    Checksum: 0x2aa2 [correct]
Session Initiation Protocol
    Status-Line: SIP/2.0 100 Trying
    Message Header
        From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
        To:sip:3768720@130.97.10.5:5060
        Call-ID:5385369e-3efe-1810-9603-8376cc92421d
        CSeq:1 NOTIFY
        Server:PBX-IP Media Gateway/2.1
        Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
        Content-Length:0

No.     Time            Source                Destination           Protocol Info
    490 09:02:49.375037 130.97.10.5           130.97.35.171         SIP      Status: 500 Internal Server Error

Frame 490 (443 bytes on wire, 443 bytes captured)
Ethernet II, Src: Cisco_f3:26:45 (00:18:ba:f3:26:45), Dst: Dell_4e:64:f8 (00:21:9b:4e:64:f8)
Internet Protocol, Src: 130.97.10.5 (130.97.10.5), Dst: 130.97.35.171 (130.97.35.171)
User Datagram Protocol, Src Port: ibm-pps (1376), Dst Port: vtsas (5070)
    Source port: ibm-pps (1376)
    Destination port: vtsas (5070)
    Length: 409
    Checksum: 0x8abc [correct]
Session Initiation Protocol
    Status-Line: SIP/2.0 500 Internal Server Error
    Message Header
        From:<sip:tes...@op...>;tag=5385369e3efe18109d428376cc92421d
        To:sip:3768720@130.97.10.5:5060;tag=27313246313536410067E556
        Call-ID:5385369e-3efe-1810-9603-8376cc92421d
        CSeq:1 NOTIFY
        Server:PBX-IP Media Gateway/2.1
        Via:SIP/2.0/UDP 130.97.35.171:5070;iid=417;branch=z9hG4bK5385369e3efe18109d438376cc92421d;uas-addr=130.97.10.5
        Content-Length:0

-----Original Message-----
From: Joegen Baclor [mailto:joe...@gm...] 
Sent: Thursday, April 16, 2009 11:11 PM
To: ope...@li...
Subject: Re: [OpenSIPStack] MWI Notify

Hi Bill,

Download the latest OpenSIPStack from CVS.   There should now be a 
sample/client_server_demo directory.  It contains the skeleton code for client and server UA.  I've used unsolicited  MWI notify in the client to 
better serve your purpose.   Here is the snippet from the Main() function. 
It basically creates two user-agents bound to 5060 and 5070 respectively and 
let the client (5070) send MWI notify to the server(5060).   You can get the 
response in OnIncomingSIPMessage of the client session.  I also pasted the 
snippet below.   Feel free to submit a tutorial based on your experience 
with this code.

HTH,
Joegen

-----------------------------

void Process::Main()
{
  #if WIN32
    SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
  #endif

  /// Create the server and and bind it to port 5060
  m_UAS = new UA();
  m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
  m_UAS->Initialize();
  m_UAS->StartTransportThreads();
  m_UAS->m_SM = new SessionManager( *m_UAS );

  /// Create the client and bind it to 5070
  m_UAC = new UA();
  m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
  m_UAC->Initialize();
  m_UAC->StartTransportThreads();
  m_UAC->m_SM = new SessionManager( *m_UAC );

  OString sesionId = ParserTools::GenGUID();
  ClientSession * session = dynamic_cast<ClientSession *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), sesionId ));
  SIPURI target( "sip:test_account@localhost:5060" );
  SIPURI localURI( "sip:tes...@op..." );
  Via localVia;
  m_UAC->ConstructVia( target.GetAddress(), localVia, SIPTransport::UDP );

  session->SetTargetURI( target );
  session->SetRemoteURI( target );
  session->SetLocalURI( localURI );
  session->SetLocalVia( localVia );

  /// Create a notify and send a test message to the server UA
  SIPMessage notify;
  if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, notify ) )
  {
    Event event( "message-summary" );
    notify.SetEvent( event );

    /// Add Event specific headers headers
    SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
    SIPHeader messageAccount( "Message-Account", "sip:test_account@localhost" );
    SIPHeader voiceMessage( "Voice-Message", "1/1" );
    notify.AddCustomHeader( messagesWaiting );
    notify.AddCustomHeader( messageAccount );
    notify.AddCustomHeader( voiceMessage );

    session->SendRequest( notify );
  }

  Sleep( 5000 );

  m_UAC->Terminate();
  m_UAS->Terminate();

  delete m_UAC;
  delete m_UAS;
}



void ClientSession::OnIncomingSIPMessage(
  SIPMessageArrival & messageEvent
)
{
  SIPMessage message = messageEvent.GetMessage();
  if( message.IsResponse() )
  {
    LOG( LogInfo(), "Got SIP Reponse" );
  }else
  {
    LOG( LogInfo(), "Got SIP Request" )
    SIPMessage response;
    message.CreateResponse( response, SIPMessage::Code200_Ok );
    SendRequest( response );
  }
  Destroy();
}


--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Friday, April 17, 2009 11:24 AM
To: "'Joegen Baclor'" <jb...@so...>; <ope...@li...>
Subject: Re: [OpenSIPStack] MWI Notify

> That's great!
>
> Thanks.
>
> -Bill
>
> -----Original Message-----
> From: Joegen Baclor [mailto:joe...@gm...]
> Sent: Thursday, April 16, 2009 6:25 PM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hey Jaimieson,
>
> I'll try to crank up a sample application for MWI as your basis.   It 
> quite
> time we put some sample tutorials in opensipstack.  Give it several hours.
>
> Joegen
>
> --------------------------------------------------
> From: "Jamieson, William W" <jam...@RL...>
> Sent: Thursday, April 16, 2009 9:35 PM
> To: <ope...@li...>
> Subject: [OpenSIPStack] MWI Notify
>
>>
>> I'm really after sending an MWI Notify and I'm using the MWIResource 
>> and MWIPackage classes. It's an unsolicited Notify so I can't see why 
>> I need a subscription but that's the way the classes were written, I 
>> think.
>>
>> For now, I have given up on the two MWI classes. This is what I have:
>>
>> Make a SIPMessage called notify which I fill with all the fields I 
>> see defined in RFC 3842 (MWI) ... (code omitted)
>>
>> Make a sessionManager
>>
>> B2BUserAgent ua("MWI");
>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>
>> Make a SIPSession:
>>
>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>> "application/reginfo+xml");    // stole this so not sure what the args 
>> are
>> OString sessionId = ParserTools::GenGUID(); SIPSession *session = 
>> sessionMgr.CreateClientSession(info, sessionId); // now I have the 
>> sessionId for the notify CallId which I add to the notify SIPMessage
>>
>> Send the request
>>
>> sessionMgr.SendRequest(invite);
>>
>> Though it compiles, I know it's not right since I'm not getting 
>> anything out on the wire. Am I even close? I thought of using this 
>> instead of the call to SendRequest but it doesn't seem right to call 
>> an event procedure directly...
>>
>> sessionMgr.OnUnsolicitedNotification(invite);
>>
>> It's very frustrating to work with no samples or docs, it's like 
>> trying to reverse engineer the whole thing. Can someone steer me to 
>> where I might find these?
>>
>> billjam
>> ---------------------------------------------------------------------
>> -
>> -------- Stay on top of everything new and different, both inside and 
>> around Java (TM) technology - register by April 22, and save $200 on 
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p 
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>> 04/15/09 19:52:00
>>
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java
> (TM) technology - register by April 22, and save $200 on the JavaOne 
> (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save $200 on 
> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date: 
> 04/16/09 16:38:00
> 

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Re: [OpenSIPStack] MWI Notify

[Jamieson, W. W <jam...@RL...>]

Looks like I can't access CVS through our Firewall. I tried Tortoise.CVS and WinCVS. When I got the code originally, I got it from the OpenSipStack Downloads page. I looked for CVS archives for opensipstack but couldn't find any. Any ideas anyone?

-----Original Message-----
From: Joegen Baclor [mailto:joe...@gm...] 
Sent: Thursday, April 16, 2009 11:11 PM
To: ope...@li...
Subject: Re: [OpenSIPStack] MWI Notify

Hi Bill,

Download the latest OpenSIPStack from CVS.   There should now be a 
sample/client_server_demo directory.  It contains the skeleton code for client and server UA.  I've used unsolicited  MWI notify in the client to 
better serve your purpose.   Here is the snippet from the Main() function. 
It basically creates two user-agents bound to 5060 and 5070 respectively and 
let the client (5070) send MWI notify to the server(5060).   You can get the 
response in OnIncomingSIPMessage of the client session.  I also pasted the 
snippet below.   Feel free to submit a tutorial based on your experience 
with this code.

HTH,
Joegen

-----------------------------

void Process::Main()
{
  #if WIN32
    SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
  #endif

  /// Create the server and and bind it to port 5060
  m_UAS = new UA();
  m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
  m_UAS->Initialize();
  m_UAS->StartTransportThreads();
  m_UAS->m_SM = new SessionManager( *m_UAS );

  /// Create the client and bind it to 5070
  m_UAC = new UA();
  m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
  m_UAC->Initialize();
  m_UAC->StartTransportThreads();
  m_UAC->m_SM = new SessionManager( *m_UAC );

  OString sesionId = ParserTools::GenGUID();
  ClientSession * session = dynamic_cast<ClientSession *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), sesionId ));
  SIPURI target( "sip:test_account@localhost:5060" );
  SIPURI localURI( "sip:tes...@op..." );
  Via localVia;
  m_UAC->ConstructVia( target.GetAddress(), localVia, SIPTransport::UDP );

  session->SetTargetURI( target );
  session->SetRemoteURI( target );
  session->SetLocalURI( localURI );
  session->SetLocalVia( localVia );

  /// Create a notify and send a test message to the server UA
  SIPMessage notify;
  if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, notify ) )
  {
    Event event( "message-summary" );
    notify.SetEvent( event );

    /// Add Event specific headers headers
    SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
    SIPHeader messageAccount( "Message-Account", "sip:test_account@localhost" );
    SIPHeader voiceMessage( "Voice-Message", "1/1" );
    notify.AddCustomHeader( messagesWaiting );
    notify.AddCustomHeader( messageAccount );
    notify.AddCustomHeader( voiceMessage );

    session->SendRequest( notify );
  }

  Sleep( 5000 );

  m_UAC->Terminate();
  m_UAS->Terminate();

  delete m_UAC;
  delete m_UAS;
}



void ClientSession::OnIncomingSIPMessage(
  SIPMessageArrival & messageEvent
)
{
  SIPMessage message = messageEvent.GetMessage();
  if( message.IsResponse() )
  {
    LOG( LogInfo(), "Got SIP Reponse" );
  }else
  {
    LOG( LogInfo(), "Got SIP Request" )
    SIPMessage response;
    message.CreateResponse( response, SIPMessage::Code200_Ok );
    SendRequest( response );
  }
  Destroy();
}


--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Friday, April 17, 2009 11:24 AM
To: "'Joegen Baclor'" <jb...@so...>; <ope...@li...>
Subject: Re: [OpenSIPStack] MWI Notify

> That's great!
>
> Thanks.
>
> -Bill
>
> -----Original Message-----
> From: Joegen Baclor [mailto:joe...@gm...]
> Sent: Thursday, April 16, 2009 6:25 PM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hey Jaimieson,
>
> I'll try to crank up a sample application for MWI as your basis.   It 
> quite
> time we put some sample tutorials in opensipstack.  Give it several hours.
>
> Joegen
>
> --------------------------------------------------
> From: "Jamieson, William W" <jam...@RL...>
> Sent: Thursday, April 16, 2009 9:35 PM
> To: <ope...@li...>
> Subject: [OpenSIPStack] MWI Notify
>
>>
>> I'm really after sending an MWI Notify and I'm using the MWIResource 
>> and MWIPackage classes. It's an unsolicited Notify so I can't see why 
>> I need a subscription but that's the way the classes were written, I 
>> think.
>>
>> For now, I have given up on the two MWI classes. This is what I have:
>>
>> Make a SIPMessage called notify which I fill with all the fields I 
>> see defined in RFC 3842 (MWI) ... (code omitted)
>>
>> Make a sessionManager
>>
>> B2BUserAgent ua("MWI");
>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>
>> Make a SIPSession:
>>
>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>> "application/reginfo+xml");    // stole this so not sure what the args 
>> are
>> OString sessionId = ParserTools::GenGUID(); SIPSession *session = 
>> sessionMgr.CreateClientSession(info, sessionId); // now I have the 
>> sessionId for the notify CallId which I add to the notify SIPMessage
>>
>> Send the request
>>
>> sessionMgr.SendRequest(invite);
>>
>> Though it compiles, I know it's not right since I'm not getting 
>> anything out on the wire. Am I even close? I thought of using this 
>> instead of the call to SendRequest but it doesn't seem right to call 
>> an event procedure directly...
>>
>> sessionMgr.OnUnsolicitedNotification(invite);
>>
>> It's very frustrating to work with no samples or docs, it's like 
>> trying to reverse engineer the whole thing. Can someone steer me to 
>> where I might find these?
>>
>> billjam
>> ---------------------------------------------------------------------
>> -
>> -------- Stay on top of everything new and different, both inside and 
>> around Java (TM) technology - register by April 22, and save $200 on 
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p 
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>> 04/15/09 19:52:00
>>
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java
> (TM) technology - register by April 22, and save $200 on the JavaOne 
> (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save $200 on 
> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date: 
> 04/16/09 16:38:00
> 

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Re: [OpenSIPStack] MWI Notify

[Jamieson, W. W <jam...@RL...>]

Delegating the tutorial to me, eh? That's fine, I don't mind paying back a little something for this great piece of work. From what I can tell from the revision history in the files, you pretty much wrote the whole thing your self. Kudos.

-Bill 

-----Original Message-----
From: Joegen Baclor [mailto:joe...@gm...] 
Sent: Thursday, April 16, 2009 11:11 PM
To: ope...@li...
Subject: Re: [OpenSIPStack] MWI Notify

Hi Bill,

Download the latest OpenSIPStack from CVS.   There should now be a 
sample/client_server_demo directory.  It contains the skeleton code for client and server UA.  I've used unsolicited  MWI notify in the client to 
better serve your purpose.   Here is the snippet from the Main() function. 
It basically creates two user-agents bound to 5060 and 5070 respectively and 
let the client (5070) send MWI notify to the server(5060).   You can get the 
response in OnIncomingSIPMessage of the client session.  I also pasted the 
snippet below.   Feel free to submit a tutorial based on your experience 
with this code.

HTH,
Joegen

-----------------------------

void Process::Main()
{
  #if WIN32
    SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
  #endif

  /// Create the server and and bind it to port 5060
  m_UAS = new UA();
  m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
  m_UAS->Initialize();
  m_UAS->StartTransportThreads();
  m_UAS->m_SM = new SessionManager( *m_UAS );

  /// Create the client and bind it to 5070
  m_UAC = new UA();
  m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
  m_UAC->Initialize();
  m_UAC->StartTransportThreads();
  m_UAC->m_SM = new SessionManager( *m_UAC );

  OString sesionId = ParserTools::GenGUID();
  ClientSession * session = dynamic_cast<ClientSession *>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), sesionId ));
  SIPURI target( "sip:test_account@localhost:5060" );
  SIPURI localURI( "sip:tes...@op..." );
  Via localVia;
  m_UAC->ConstructVia( target.GetAddress(), localVia, SIPTransport::UDP );

  session->SetTargetURI( target );
  session->SetRemoteURI( target );
  session->SetLocalURI( localURI );
  session->SetLocalVia( localVia );

  /// Create a notify and send a test message to the server UA
  SIPMessage notify;
  if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, notify ) )
  {
    Event event( "message-summary" );
    notify.SetEvent( event );

    /// Add Event specific headers headers
    SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
    SIPHeader messageAccount( "Message-Account", "sip:test_account@localhost" );
    SIPHeader voiceMessage( "Voice-Message", "1/1" );
    notify.AddCustomHeader( messagesWaiting );
    notify.AddCustomHeader( messageAccount );
    notify.AddCustomHeader( voiceMessage );

    session->SendRequest( notify );
  }

  Sleep( 5000 );

  m_UAC->Terminate();
  m_UAS->Terminate();

  delete m_UAC;
  delete m_UAS;
}



void ClientSession::OnIncomingSIPMessage(
  SIPMessageArrival & messageEvent
)
{
  SIPMessage message = messageEvent.GetMessage();
  if( message.IsResponse() )
  {
    LOG( LogInfo(), "Got SIP Reponse" );
  }else
  {
    LOG( LogInfo(), "Got SIP Request" )
    SIPMessage response;
    message.CreateResponse( response, SIPMessage::Code200_Ok );
    SendRequest( response );
  }
  Destroy();
}


--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Friday, April 17, 2009 11:24 AM
To: "'Joegen Baclor'" <jb...@so...>; <ope...@li...>
Subject: Re: [OpenSIPStack] MWI Notify

> That's great!
>
> Thanks.
>
> -Bill
>
> -----Original Message-----
> From: Joegen Baclor [mailto:joe...@gm...]
> Sent: Thursday, April 16, 2009 6:25 PM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hey Jaimieson,
>
> I'll try to crank up a sample application for MWI as your basis.   It 
> quite
> time we put some sample tutorials in opensipstack.  Give it several hours.
>
> Joegen
>
> --------------------------------------------------
> From: "Jamieson, William W" <jam...@RL...>
> Sent: Thursday, April 16, 2009 9:35 PM
> To: <ope...@li...>
> Subject: [OpenSIPStack] MWI Notify
>
>>
>> I'm really after sending an MWI Notify and I'm using the MWIResource 
>> and MWIPackage classes. It's an unsolicited Notify so I can't see why 
>> I need a subscription but that's the way the classes were written, I 
>> think.
>>
>> For now, I have given up on the two MWI classes. This is what I have:
>>
>> Make a SIPMessage called notify which I fill with all the fields I 
>> see defined in RFC 3842 (MWI) ... (code omitted)
>>
>> Make a sessionManager
>>
>> B2BUserAgent ua("MWI");
>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>
>> Make a SIPSession:
>>
>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>> "application/reginfo+xml");    // stole this so not sure what the args 
>> are
>> OString sessionId = ParserTools::GenGUID(); SIPSession *session = 
>> sessionMgr.CreateClientSession(info, sessionId); // now I have the 
>> sessionId for the notify CallId which I add to the notify SIPMessage
>>
>> Send the request
>>
>> sessionMgr.SendRequest(invite);
>>
>> Though it compiles, I know it's not right since I'm not getting 
>> anything out on the wire. Am I even close? I thought of using this 
>> instead of the call to SendRequest but it doesn't seem right to call 
>> an event procedure directly...
>>
>> sessionMgr.OnUnsolicitedNotification(invite);
>>
>> It's very frustrating to work with no samples or docs, it's like 
>> trying to reverse engineer the whole thing. Can someone steer me to 
>> where I might find these?
>>
>> billjam
>> ---------------------------------------------------------------------
>> -
>> -------- Stay on top of everything new and different, both inside and 
>> around Java (TM) technology - register by April 22, and save $200 on 
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p 
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>> 04/15/09 19:52:00
>>
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java
> (TM) technology - register by April 22, and save $200 on the JavaOne 
> (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save $200 on 
> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date: 
> 04/16/09 16:38:00
> 

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Re: [OpenSIPStack] MWI Notify

[Joegen B. <joe...@gm...>]

Hi Bill,

Download the latest OpenSIPStack from CVS.   There should now be a 
sample/client_server_demo directory.  It contains the skeleton code for 
client and server UA.  I've used unsolicited  MWI notify in the client to 
better serve your purpose.   Here is the snippet from the Main() function. 
It basically creates two user-agents bound to 5060 and 5070 respectively and 
let the client (5070) send MWI notify to the server(5060).   You can get the 
response in OnIncomingSIPMessage of the client session.  I also pasted the 
snippet below.   Feel free to submit a tutorial based on your experience 
with this code.

HTH,
Joegen

-----------------------------

void Process::Main()
{
  #if WIN32
    SetConsoleCtrlHandler(Win32SignalHandler, TRUE);
  #endif

  /// Create the server and and bind it to port 5060
  m_UAS = new UA();
  m_UAS->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5060 );
  m_UAS->Initialize();
  m_UAS->StartTransportThreads();
  m_UAS->m_SM = new SessionManager( *m_UAS );

  /// Create the client and bind it to 5070
  m_UAC = new UA();
  m_UAC->GetDefaultProfile().GetTransportProfile().EnableUDP( 0, 5070 );
  m_UAC->Initialize();
  m_UAC->StartTransportThreads();
  m_UAC->m_SM = new SessionManager( *m_UAC );

  OString sesionId = ParserTools::GenGUID();
  ClientSession * session = dynamic_cast<ClientSession 
*>(m_UAC->m_SM->CreateClientSession(  m_UAC->GetDefaultProfile(), 
sesionId ));
  SIPURI target( "sip:test_account@localhost:5060" );
  SIPURI localURI( "sip:tes...@op..." );
  Via localVia;
  m_UAC->ConstructVia( target.GetAddress(), localVia, SIPTransport::UDP );

  session->SetTargetURI( target );
  session->SetRemoteURI( target );
  session->SetLocalURI( localURI );
  session->SetLocalVia( localVia );

  /// Create a notify and send a test message to the server UA
  SIPMessage notify;
  if( session->CreateRequestOutOfDialog( SIPMessage::Method_NOTIFY, 
notify ) )
  {
    Event event( "message-summary" );
    notify.SetEvent( event );

    /// Add Event specific headers headers
    SIPHeader messagesWaiting( "Messages-Waiting", "yes" );
    SIPHeader messageAccount( "Message-Account", 
"sip:test_account@localhost" );
    SIPHeader voiceMessage( "Voice-Message", "1/1" );
    notify.AddCustomHeader( messagesWaiting );
    notify.AddCustomHeader( messageAccount );
    notify.AddCustomHeader( voiceMessage );

    session->SendRequest( notify );
  }

  Sleep( 5000 );

  m_UAC->Terminate();
  m_UAS->Terminate();

  delete m_UAC;
  delete m_UAS;
}



void ClientSession::OnIncomingSIPMessage(
  SIPMessageArrival & messageEvent
)
{
  SIPMessage message = messageEvent.GetMessage();
  if( message.IsResponse() )
  {
    LOG( LogInfo(), "Got SIP Reponse" );
  }else
  {
    LOG( LogInfo(), "Got SIP Request" )
    SIPMessage response;
    message.CreateResponse( response, SIPMessage::Code200_Ok );
    SendRequest( response );
  }
  Destroy();
}


--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Friday, April 17, 2009 11:24 AM
To: "'Joegen Baclor'" <jb...@so...>; 
<ope...@li...>
Subject: Re: [OpenSIPStack] MWI Notify

> That's great!
>
> Thanks.
>
> -Bill
>
> -----Original Message-----
> From: Joegen Baclor [mailto:joe...@gm...]
> Sent: Thursday, April 16, 2009 6:25 PM
> To: ope...@li...
> Subject: Re: [OpenSIPStack] MWI Notify
>
> Hey Jaimieson,
>
> I'll try to crank up a sample application for MWI as your basis.   It 
> quite
> time we put some sample tutorials in opensipstack.  Give it several hours.
>
> Joegen
>
> --------------------------------------------------
> From: "Jamieson, William W" <jam...@RL...>
> Sent: Thursday, April 16, 2009 9:35 PM
> To: <ope...@li...>
> Subject: [OpenSIPStack] MWI Notify
>
>>
>> I'm really after sending an MWI Notify and I'm using the MWIResource
>> and MWIPackage classes. It's an unsolicited Notify so I can't see why
>> I need a subscription but that's the way the classes were written, I 
>> think.
>>
>> For now, I have given up on the two MWI classes. This is what I have:
>>
>> Make a SIPMessage called notify which I fill with all the fields I see
>> defined in RFC 3842 (MWI) ... (code omitted)
>>
>> Make a sessionManager
>>
>> B2BUserAgent ua("MWI");
>> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>>
>> Make a SIPSession:
>>
>> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI,
>> "application/reginfo+xml");    // stole this so not sure what the args 
>> are
>> OString sessionId = ParserTools::GenGUID(); SIPSession *session =
>> sessionMgr.CreateClientSession(info, sessionId); // now I have the
>> sessionId for the notify CallId which I add to the notify SIPMessage
>>
>> Send the request
>>
>> sessionMgr.SendRequest(invite);
>>
>> Though it compiles, I know it's not right since I'm not getting
>> anything out on the wire. Am I even close? I thought of using this
>> instead of the call to SendRequest but it doesn't seem right to call
>> an event procedure directly...
>>
>> sessionMgr.OnUnsolicitedNotification(invite);
>>
>> It's very frustrating to work with no samples or docs, it's like
>> trying to reverse engineer the whole thing. Can someone steer me to
>> where I might find these?
>>
>> billjam
>> ----------------------------------------------------------------------
>> -------- Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save $200 on
>> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date:
>> 04/15/09 19:52:00
>>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and around Java 
> (TM) technology - register by April 22, and save $200 on the JavaOne (SM) 
> conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.59/2063 - Release Date: 04/16/09 
> 16:38:00
> 

Re: [OpenSIPStack] MWI Notify

[Jamieson, W. W <jam...@RL...>]

That's great!

Thanks.

-Bill 

-----Original Message-----
From: Joegen Baclor [mailto:joe...@gm...] 
Sent: Thursday, April 16, 2009 6:25 PM
To: ope...@li...
Subject: Re: [OpenSIPStack] MWI Notify

Hey Jaimieson,

I'll try to crank up a sample application for MWI as your basis.   It quite 
time we put some sample tutorials in opensipstack.  Give it several hours.

Joegen

--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Thursday, April 16, 2009 9:35 PM
To: <ope...@li...>
Subject: [OpenSIPStack] MWI Notify

>
> I'm really after sending an MWI Notify and I'm using the MWIResource 
> and MWIPackage classes. It's an unsolicited Notify so I can't see why 
> I need a subscription but that's the way the classes were written, I think.
>
> For now, I have given up on the two MWI classes. This is what I have:
>
> Make a SIPMessage called notify which I fill with all the fields I see 
> defined in RFC 3842 (MWI) ... (code omitted)
>
> Make a sessionManager
>
> B2BUserAgent ua("MWI");
> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>
> Make a SIPSession:
>
> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI, 
> "application/reginfo+xml");    // stole this so not sure what the args are
> OString sessionId = ParserTools::GenGUID(); SIPSession *session = 
> sessionMgr.CreateClientSession(info, sessionId); // now I have the 
> sessionId for the notify CallId which I add to the notify SIPMessage
>
> Send the request
>
> sessionMgr.SendRequest(invite);
>
> Though it compiles, I know it's not right since I'm not getting 
> anything out on the wire. Am I even close? I thought of using this 
> instead of the call to SendRequest but it doesn't seem right to call 
> an event procedure directly...
>
> sessionMgr.OnUnsolicitedNotification(invite);
>
> It's very frustrating to work with no samples or docs, it's like 
> trying to reverse engineer the whole thing. Can someone steer me to 
> where I might find these?
>
> billjam
> ----------------------------------------------------------------------
> -------- Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save $200 on 
> the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p 
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date: 
> 04/15/09 19:52:00
> 

------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today. 
Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________
opensipstack-devel mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

Re: [OpenSIPStack] MWI Notify

[Joegen B. <joe...@gm...>]

Hey Jaimieson,

I'll try to crank up a sample application for MWI as your basis.   It quite 
time we put some sample tutorials in opensipstack.  Give it several hours.

Joegen

--------------------------------------------------
From: "Jamieson, William W" <jam...@RL...>
Sent: Thursday, April 16, 2009 9:35 PM
To: <ope...@li...>
Subject: [OpenSIPStack] MWI Notify

>
> I'm really after sending an MWI Notify and I'm using the MWIResource and 
> MWIPackage classes. It's an unsolicited Notify so I can't see why I need a 
> subscription but that's the way the classes were written, I think.
>
> For now, I have given up on the two MWI classes. This is what I have:
>
> Make a SIPMessage called notify which I fill with all the fields I see 
> defined in RFC 3842 (MWI)
> ... (code omitted)
>
> Make a sessionManager
>
> B2BUserAgent ua("MWI");
> RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);
>
> Make a SIPSession:
>
> RFC3265ClientManager::SubscriptionInfo info("reg", fromURI, 
> "application/reginfo+xml");    // stole this so not sure what the args are
> OString sessionId = ParserTools::GenGUID();
> SIPSession *session = sessionMgr.CreateClientSession(info, sessionId);
> // now I have the sessionId for the notify CallId which I add to the 
> notify SIPMessage
>
> Send the request
>
> sessionMgr.SendRequest(invite);
>
> Though it compiles, I know it's not right since I'm not getting anything 
> out on the wire. Am I even close? I thought of using this instead of the 
> call to SendRequest but it doesn't seem right to call an event procedure 
> directly...
>
> sessionMgr.OnUnsolicitedNotification(invite);
>
> It's very frustrating to work with no samples or docs, it's like trying to 
> reverse engineer the whole thing. Can someone steer me to where I might 
> find these?
>
> billjam
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.58/2061 - Release Date: 04/15/09 
> 19:52:00
> 

[OpenSIPStack] MWI Notify

[Jamieson, W. W <jam...@RL...>]

I'm really after sending an MWI Notify and I'm using the MWIResource and MWIPackage classes. It's an unsolicited Notify so I can't see why I need a subscription but that's the way the classes were written, I think.

For now, I have given up on the two MWI classes. This is what I have:

Make a SIPMessage called notify which I fill with all the fields I see defined in RFC 3842 (MWI)
... (code omitted)

Make a sessionManager

B2BUserAgent ua("MWI");
RFC3265ClientManager sessionMgr(ua, "MWI", 1, 1024 * 2);

Make a SIPSession:

RFC3265ClientManager::SubscriptionInfo info("reg", fromURI, "application/reginfo+xml");    // stole this so not sure what the args are
OString sessionId = ParserTools::GenGUID();
SIPSession *session = sessionMgr.CreateClientSession(info, sessionId);
// now I have the sessionId for the notify CallId which I add to the notify SIPMessage

Send the request

sessionMgr.SendRequest(invite);

Though it compiles, I know it's not right since I'm not getting anything out on the wire. Am I even close? I thought of using this instead of the call to SendRequest but it doesn't seem right to call an event procedure directly...

sessionMgr.OnUnsolicitedNotification(invite);

It's very frustrating to work with no samples or docs, it's like trying to reverse engineer the whole thing. Can someone steer me to where I might find these?

billjam

[OpenSIPStack] SUBSCRIBE support

[Ramu <con...@gm...>]

Hi,

At present OpenSBC reply with "420 Bad Extension" for SUBSCRIBE message.

When are we planning for SUBSCRIBE support in OpenSBC?

Thanks
Ramu

[OpenSIPStack] how to write server application..

[kishore k. <kk...@gm...>]

Hi,

Can anyone tell me how to write a server side application to listen for the
call backs when sending MESSAGE method from client side.

Regards,
Kishore.

Re: [OpenSIPStack] OpenSBC UpperRegistration Query

[Joegen B. <joe...@gm...>]

That's great news.  Glad to hear you got it working.

--------------------------------------------------
From: "Ramu" <con...@gm...>
Sent: Wednesday, April 15, 2009 1:06 PM
To: "Joegen Baclor" <jo...@op...>; 
<ope...@li...>
Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query

> Hi,
>
> After upgrading to SVN version upper registration and calls are working
> fine.
>
> Thanks for your help!
>
> On Tue, Apr 14, 2009 at 2:31 PM, Ramu <con...@gm...> wrote:
>
>> Yes!
>>
>>
>> On Tue, Apr 14, 2009 at 1:16 PM, Joegen Baclor 
>> <joe...@gm...>wrote:
>>
>>> I meant the OpenSIPStack library.  Not OpenSBC.  Are you using the 
>>> latest
>>> library as well?
>>>
>>> --------------------------------------------------
>>> From: "Ramu" <con...@gm...>
>>> Sent: Tuesday, April 14, 2009 2:42 PM
>>> To: "Joegen Baclor" <jb...@so...>
>>> Cc: <ope...@li...>
>>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>>>
>>> > Hi,
>>> >
>>> > Yes Am using latest version.  Following are my version details:
>>> >
>>> > [root@as1 distrib]# ./opensbc -v
>>> > Product Name: OpenSBC
>>> > Manufacturer: opensipstack.org
>>> > Version     : 1.1.5-96
>>> > System      : Linux-i686 2.6.18-92.1.18.el5.028stab060.2PAE
>>> > Release-Date: Mar 30 2009 16:27:46
>>> >
>>> >
>>> > On Tue, Apr 14, 2009 at 11:26 AM, Joegen Baclor
>>> > <joe...@gm...>wrote:
>>> >
>>> >> Ramu,
>>> >>
>>> >> By any chance, are you using the recent version of the OpenSIPStack
>>> >> library
>>> >> as well?  There was a bug in record-routing in previous commits where
>>> the
>>> >> port is not sepcified in the Record-Route.   It seems the log 
>>> >> indicates
>>> >> that
>>> >> you are suffering from this bug
>>> >>
>>> >> Joegen
>>> >>
>>> >> --------------------------------------------------
>>> >> From: "Joegen Baclor" <joe...@gm...>
>>> >> Sent: Tuesday, April 14, 2009 1:17 PM
>>> >> To: "Ramu" <con...@gm...>; <
>>> >> ope...@li...>
>>> >>
>>> >> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>>> >>
>>> >>  I GREPed all the ACKs sent by opensbc from the log you sent.  Which
>>> >> among
>>> >>> this ACK requests are getting sent to the the wrong destination
>>> (DST:)?
>>> >>>
>>> >>> 2009/04/02 15:45:59.029 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 59.93.81.139:55128:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=421
>>> >>> 2009/04/02 15:45:59.035 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> >>> bytes=466
>>> >>> 2009/04/02 15:45:59.039 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=496
>>> >>> 2009/04/02 15:45:59.540 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=496
>>> >>> 2009/04/02 15:45:59.545 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> >>> bytes=466
>>> >>> 2009/04/02 15:46:00.041 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=496
>>> >>> 2009/04/02 15:46:00.350 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> >>> bytes=466
>>> >>> 2009/04/02 15:46:01.045 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=496
>>> >>> 2009/04/02 15:46:01.354 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> >>> bytes=466
>>> >>> 2009/04/02 15:46:03.054 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=496
>>> >>> 2009/04/02 15:46:03.363 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> >>> bytes=466
>>> >>> 2009/04/02 15:46:03.557 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=496
>>> >>> 2009/04/02 15:46:03.866 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> >>> bytes=466
>>> >>> 2009/04/02 15:46:04.060 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> >>> bytes=496
>>> >>> 2009/04/02 15:46:04.369 INF: [CID=0x9a9e4b05] >>> ACK
>>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> >>> bytes=466
>>> >>>
>>> >>>
>>> >>> From: Ramu
>>> >>> Sent: Tuesday, April 14, 2009 12:58 PM
>>> >>> To: Joegen Baclor ; ope...@li...
>>> >>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>>> >>>
>>> >>>
>>> >>> Hi,
>>> >>>
>>> >>> Thanks for your quick reply.
>>> >>>
>>> >>> I am here with attaching level 5 log files
>>> >>> 1) opensbc-invite-private-contact.zip file, it shows ACK problem 
>>> >>> (ACK
>>> is
>>> >>> going to private contact)
>>> >>> 2) opensbc-register.zip file, it shows REGISTER log file.
>>> >>>
>>> >>>
>>> >>>
>>> >>> On Tue, Apr 14, 2009 at 6:38 AM, Joegen Baclor <
>>> joe...@gm...>
>>> >>> wrote:
>>> >>>
>>> >>>  I don't get it.  ACK is a mid-dialog request and has nothing to do
>>> with
>>> >>> the
>>> >>>  Registration contact.  The registration contact would only be
>>> >>> significant
>>> >>>  when routing INVITE.   The fact that the call reaches the 
>>> >>> destination
>>> >>> UA
>>> >>>  proves that everything is in order as far as routing through the
>>> >>> registrar
>>> >>>  is concerned.   Please send an ethereal capture as well as the 
>>> >>> level
>>> 5
>>> >>> log
>>> >>>  of OpenSBC so we can see what is exactly happening to the ACK.
>>> >>>
>>> >>>  Joegen
>>> >>>
>>> >>>  --------------------------------------------------
>>> >>>
>>> >>>  From: "Ramu" <con...@gm...>
>>> >>>
>>> >>>  Sent: Tuesday, April 14, 2009 1:05 AM
>>> >>>
>>> >>>  To: <ope...@li...>
>>> >>>
>>> >>>  Subject: [OpenSIPStack] OpenSBC UpperRegistration Query
>>> >>>
>>> >>>
>>> >>>  > Hi,
>>> >>>  >
>>> >>>  > We are using OpenSBC in upper registration mode.
>>> >>>  >
>>> >>>  > When we register phones OpenSBC storing private contact (please 
>>> >>> see
>>> >>> the
>>> >>>  > attachment)
>>> >>>  >
>>> >>>  > As it is storing private contact when we try to make calls to
>>> >>> registered
>>> >>>  > user ACK is going to private contact which is not reaching phone.
>>> >>>  >
>>> >>>  > Please see full details of this problem in below thread.
>>> >>>  >
>>> >>>  > http://www.opensourcesip.org:8080/clearspacex/message/9442
>>> >>>  >
>>> >>>  > I appreciate your hep.
>>> >>>  >
>>> >>>  > Thanks,
>>> >>>  > Ramu
>>> >>>  >
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>  >
>>> >>>
>>> ------------------------------------------------------------------------------
>>> >>>  > This SF.net email is sponsored by:
>>> >>>  > High Quality Requirements in a Collaborative Environment.
>>> >>>  > Download a free trial of Rational Requirements Composer Now!
>>> >>>  > http://p.sf.net/sfu/www-ibm-com
>>> >>>
>>> >>>
>>> >>>
>>> >>>  > _______________________________________________
>>> >>>  > opensipstack-devel mailing list
>>> >>>
>>> >>>  > ope...@li...
>>> >>>
>>> >>>  > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>> >>>  >
>>> >>>
>>> >>>
>>> >>>
>>> >>>  >
>>> >>>  > No virus found in this incoming message.
>>> >>>  > Checked by AVG - www.avg.com
>>> >>>  > Version: 8.0.238 / Virus Database: 270.11.54/2055 - Release Date:
>>> >>> 04/12/09
>>> >>>  > 13:14:00
>>> >>>  >
>>> >>>
>>> >>>
>>> >>>
>>>  ------------------------------------------------------------------------------
>>> >>>  This SF.net email is sponsored by:
>>> >>>  High Quality Requirements in a Collaborative Environment.
>>> >>>  Download a free trial of Rational Requirements Composer Now!
>>> >>>  http://p.sf.net/sfu/www-ibm-com
>>> >>>  _______________________________________________
>>> >>>  opensipstack-devel mailing list
>>> >>>
>>> >>>  ope...@li...
>>> >>>
>>> >>>  https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>> --
>>> >>> Ramu
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> >>>
>>> --------------------------------------------------------------------------------
>>> >>>
>>> >>>
>>> >>>
>>> >>> No virus found in this incoming message.
>>> >>> Checked by AVG - www.avg.com
>>> >>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
>>> >>> 04/13/09
>>> >>> 17:56:00
>>> >>>
>>> >>>
>>> ------------------------------------------------------------------------------
>>> >>> This SF.net email is sponsored by:
>>> >>> High Quality Requirements in a Collaborative Environment.
>>> >>> Download a free trial of Rational Requirements Composer Now!
>>> >>> http://p.sf.net/sfu/www-ibm-com
>>> >>> _______________________________________________
>>> >>> opensipstack-devel mailing list
>>> >>> ope...@li...
>>> >>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>> >>>
>>> >>
>>> >>
>>> >>
>>> >>
>>> >>> No virus found in this incoming message.
>>> >>> Checked by AVG - www.avg.com
>>> >>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
>>> >>> 04/13/09
>>> >>> 17:56:00
>>> >>>
>>> >>>
>>> >
>>> >
>>> > --
>>> > Ramu
>>> >
>>> ------------------------------------------------------------------------------
>>> > This SF.net email is sponsored by:
>>> > High Quality Requirements in a Collaborative Environment.
>>> > Download a free trial of Rational Requirements Composer Now!
>>> > http://p.sf.net/sfu/www-ibm-com
>>> > _______________________________________________
>>> > opensipstack-devel mailing list
>>> > ope...@li...
>>> > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>> >
>>>
>>>
>>>
>>> >
>>> > No virus found in this incoming message.
>>> > Checked by AVG - www.avg.com
>>> > Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
>>> 04/13/09
>>> > 17:56:00
>>> >
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> High Quality Requirements in a Collaborative Environment.
>>> Download a free trial of Rational Requirements Composer Now!
>>> http://p.sf.net/sfu/www-ibm-com
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>
>>
>>
>> --
>> Ramu
>>
>
>
>
> -- 
> Ramu
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.57/2059 - Release Date: 04/14/09 
> 14:52:00
> 

Re: [OpenSIPStack] OpenSBC UpperRegistration Query

[Ramu <con...@gm...>]

Hi,

After upgrading to SVN version upper registration and calls are working
fine.

Thanks for your help!

On Tue, Apr 14, 2009 at 2:31 PM, Ramu <con...@gm...> wrote:

> Yes!
>
>
> On Tue, Apr 14, 2009 at 1:16 PM, Joegen Baclor <joe...@gm...>wrote:
>
>> I meant the OpenSIPStack library.  Not OpenSBC.  Are you using the latest
>> library as well?
>>
>> --------------------------------------------------
>> From: "Ramu" <con...@gm...>
>> Sent: Tuesday, April 14, 2009 2:42 PM
>> To: "Joegen Baclor" <jb...@so...>
>> Cc: <ope...@li...>
>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>>
>> > Hi,
>> >
>> > Yes Am using latest version.  Following are my version details:
>> >
>> > [root@as1 distrib]# ./opensbc -v
>> > Product Name: OpenSBC
>> > Manufacturer: opensipstack.org
>> > Version     : 1.1.5-96
>> > System      : Linux-i686 2.6.18-92.1.18.el5.028stab060.2PAE
>> > Release-Date: Mar 30 2009 16:27:46
>> >
>> >
>> > On Tue, Apr 14, 2009 at 11:26 AM, Joegen Baclor
>> > <joe...@gm...>wrote:
>> >
>> >> Ramu,
>> >>
>> >> By any chance, are you using the recent version of the OpenSIPStack
>> >> library
>> >> as well?  There was a bug in record-routing in previous commits where
>> the
>> >> port is not sepcified in the Record-Route.   It seems the log indicates
>> >> that
>> >> you are suffering from this bug
>> >>
>> >> Joegen
>> >>
>> >> --------------------------------------------------
>> >> From: "Joegen Baclor" <joe...@gm...>
>> >> Sent: Tuesday, April 14, 2009 1:17 PM
>> >> To: "Ramu" <con...@gm...>; <
>> >> ope...@li...>
>> >>
>> >> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>> >>
>> >>  I GREPed all the ACKs sent by opensbc from the log you sent.  Which
>> >> among
>> >>> this ACK requests are getting sent to the the wrong destination
>> (DST:)?
>> >>>
>> >>> 2009/04/02 15:45:59.029 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 59.93.81.139:55128:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=421
>> >>> 2009/04/02 15:45:59.035 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> >>> bytes=466
>> >>> 2009/04/02 15:45:59.039 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=496
>> >>> 2009/04/02 15:45:59.540 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=496
>> >>> 2009/04/02 15:45:59.545 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> >>> bytes=466
>> >>> 2009/04/02 15:46:00.041 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=496
>> >>> 2009/04/02 15:46:00.350 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> >>> bytes=466
>> >>> 2009/04/02 15:46:01.045 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=496
>> >>> 2009/04/02 15:46:01.354 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> >>> bytes=466
>> >>> 2009/04/02 15:46:03.054 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=496
>> >>> 2009/04/02 15:46:03.363 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> >>> bytes=466
>> >>> 2009/04/02 15:46:03.557 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=496
>> >>> 2009/04/02 15:46:03.866 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> >>> bytes=466
>> >>> 2009/04/02 15:46:04.060 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> >>> bytes=496
>> >>> 2009/04/02 15:46:04.369 INF: [CID=0x9a9e4b05] >>> ACK
>> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> >>> bytes=466
>> >>>
>> >>>
>> >>> From: Ramu
>> >>> Sent: Tuesday, April 14, 2009 12:58 PM
>> >>> To: Joegen Baclor ; ope...@li...
>> >>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>> >>>
>> >>>
>> >>> Hi,
>> >>>
>> >>> Thanks for your quick reply.
>> >>>
>> >>> I am here with attaching level 5 log files
>> >>> 1) opensbc-invite-private-contact.zip file, it shows ACK problem (ACK
>> is
>> >>> going to private contact)
>> >>> 2) opensbc-register.zip file, it shows REGISTER log file.
>> >>>
>> >>>
>> >>>
>> >>> On Tue, Apr 14, 2009 at 6:38 AM, Joegen Baclor <
>> joe...@gm...>
>> >>> wrote:
>> >>>
>> >>>  I don't get it.  ACK is a mid-dialog request and has nothing to do
>> with
>> >>> the
>> >>>  Registration contact.  The registration contact would only be
>> >>> significant
>> >>>  when routing INVITE.   The fact that the call reaches the destination
>> >>> UA
>> >>>  proves that everything is in order as far as routing through the
>> >>> registrar
>> >>>  is concerned.   Please send an ethereal capture as well as the level
>> 5
>> >>> log
>> >>>  of OpenSBC so we can see what is exactly happening to the ACK.
>> >>>
>> >>>  Joegen
>> >>>
>> >>>  --------------------------------------------------
>> >>>
>> >>>  From: "Ramu" <con...@gm...>
>> >>>
>> >>>  Sent: Tuesday, April 14, 2009 1:05 AM
>> >>>
>> >>>  To: <ope...@li...>
>> >>>
>> >>>  Subject: [OpenSIPStack] OpenSBC UpperRegistration Query
>> >>>
>> >>>
>> >>>  > Hi,
>> >>>  >
>> >>>  > We are using OpenSBC in upper registration mode.
>> >>>  >
>> >>>  > When we register phones OpenSBC storing private contact (please see
>> >>> the
>> >>>  > attachment)
>> >>>  >
>> >>>  > As it is storing private contact when we try to make calls to
>> >>> registered
>> >>>  > user ACK is going to private contact which is not reaching phone.
>> >>>  >
>> >>>  > Please see full details of this problem in below thread.
>> >>>  >
>> >>>  > http://www.opensourcesip.org:8080/clearspacex/message/9442
>> >>>  >
>> >>>  > I appreciate your hep.
>> >>>  >
>> >>>  > Thanks,
>> >>>  > Ramu
>> >>>  >
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>  >
>> >>>
>> ------------------------------------------------------------------------------
>> >>>  > This SF.net email is sponsored by:
>> >>>  > High Quality Requirements in a Collaborative Environment.
>> >>>  > Download a free trial of Rational Requirements Composer Now!
>> >>>  > http://p.sf.net/sfu/www-ibm-com
>> >>>
>> >>>
>> >>>
>> >>>  > _______________________________________________
>> >>>  > opensipstack-devel mailing list
>> >>>
>> >>>  > ope...@li...
>> >>>
>> >>>  > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>> >>>  >
>> >>>
>> >>>
>> >>>
>> >>>  >
>> >>>  > No virus found in this incoming message.
>> >>>  > Checked by AVG - www.avg.com
>> >>>  > Version: 8.0.238 / Virus Database: 270.11.54/2055 - Release Date:
>> >>> 04/12/09
>> >>>  > 13:14:00
>> >>>  >
>> >>>
>> >>>
>> >>>
>>  ------------------------------------------------------------------------------
>> >>>  This SF.net email is sponsored by:
>> >>>  High Quality Requirements in a Collaborative Environment.
>> >>>  Download a free trial of Rational Requirements Composer Now!
>> >>>  http://p.sf.net/sfu/www-ibm-com
>> >>>  _______________________________________________
>> >>>  opensipstack-devel mailing list
>> >>>
>> >>>  ope...@li...
>> >>>
>> >>>  https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Ramu
>> >>>
>> >>>
>> >>>
>> >>>
>> >>>
>> --------------------------------------------------------------------------------
>> >>>
>> >>>
>> >>>
>> >>> No virus found in this incoming message.
>> >>> Checked by AVG - www.avg.com
>> >>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
>> >>> 04/13/09
>> >>> 17:56:00
>> >>>
>> >>>
>> ------------------------------------------------------------------------------
>> >>> This SF.net email is sponsored by:
>> >>> High Quality Requirements in a Collaborative Environment.
>> >>> Download a free trial of Rational Requirements Composer Now!
>> >>> http://p.sf.net/sfu/www-ibm-com
>> >>> _______________________________________________
>> >>> opensipstack-devel mailing list
>> >>> ope...@li...
>> >>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>> >>>
>> >>
>> >>
>> >>
>> >>
>> >>> No virus found in this incoming message.
>> >>> Checked by AVG - www.avg.com
>> >>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
>> >>> 04/13/09
>> >>> 17:56:00
>> >>>
>> >>>
>> >
>> >
>> > --
>> > Ramu
>> >
>> ------------------------------------------------------------------------------
>> > This SF.net email is sponsored by:
>> > High Quality Requirements in a Collaborative Environment.
>> > Download a free trial of Rational Requirements Composer Now!
>> > http://p.sf.net/sfu/www-ibm-com
>> > _______________________________________________
>> > opensipstack-devel mailing list
>> > ope...@li...
>> > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>> >
>>
>>
>>
>> >
>> > No virus found in this incoming message.
>> > Checked by AVG - www.avg.com
>> > Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
>> 04/13/09
>> > 17:56:00
>> >
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> High Quality Requirements in a Collaborative Environment.
>> Download a free trial of Rational Requirements Composer Now!
>> http://p.sf.net/sfu/www-ibm-com
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>
>
>
> --
> Ramu
>



-- 
Ramu

Re: [OpenSIPStack] OpenSBC UpperRegistration Query

[Ramu <con...@gm...>]

Yes!

On Tue, Apr 14, 2009 at 1:16 PM, Joegen Baclor <joe...@gm...>wrote:

> I meant the OpenSIPStack library.  Not OpenSBC.  Are you using the latest
> library as well?
>
> --------------------------------------------------
> From: "Ramu" <con...@gm...>
> Sent: Tuesday, April 14, 2009 2:42 PM
> To: "Joegen Baclor" <jb...@so...>
> Cc: <ope...@li...>
> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>
> > Hi,
> >
> > Yes Am using latest version.  Following are my version details:
> >
> > [root@as1 distrib]# ./opensbc -v
> > Product Name: OpenSBC
> > Manufacturer: opensipstack.org
> > Version     : 1.1.5-96
> > System      : Linux-i686 2.6.18-92.1.18.el5.028stab060.2PAE
> > Release-Date: Mar 30 2009 16:27:46
> >
> >
> > On Tue, Apr 14, 2009 at 11:26 AM, Joegen Baclor
> > <joe...@gm...>wrote:
> >
> >> Ramu,
> >>
> >> By any chance, are you using the recent version of the OpenSIPStack
> >> library
> >> as well?  There was a bug in record-routing in previous commits where
> the
> >> port is not sepcified in the Record-Route.   It seems the log indicates
> >> that
> >> you are suffering from this bug
> >>
> >> Joegen
> >>
> >> --------------------------------------------------
> >> From: "Joegen Baclor" <joe...@gm...>
> >> Sent: Tuesday, April 14, 2009 1:17 PM
> >> To: "Ramu" <con...@gm...>; <
> >> ope...@li...>
> >>
> >> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
> >>
> >>  I GREPed all the ACKs sent by opensbc from the log you sent.  Which
> >> among
> >>> this ACK requests are getting sent to the the wrong destination (DST:)?
> >>>
> >>> 2009/04/02 15:45:59.029 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 59.93.81.139:55128:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=421
> >>> 2009/04/02 15:45:59.035 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
> >>> bytes=466
> >>> 2009/04/02 15:45:59.039 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=496
> >>> 2009/04/02 15:45:59.540 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=496
> >>> 2009/04/02 15:45:59.545 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
> >>> bytes=466
> >>> 2009/04/02 15:46:00.041 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=496
> >>> 2009/04/02 15:46:00.350 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
> >>> bytes=466
> >>> 2009/04/02 15:46:01.045 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=496
> >>> 2009/04/02 15:46:01.354 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
> >>> bytes=466
> >>> 2009/04/02 15:46:03.054 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=496
> >>> 2009/04/02 15:46:03.363 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
> >>> bytes=466
> >>> 2009/04/02 15:46:03.557 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=496
> >>> 2009/04/02 15:46:03.866 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
> >>> bytes=466
> >>> 2009/04/02 15:46:04.060 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
> >>> bytes=496
> >>> 2009/04/02 15:46:04.369 INF: [CID=0x9a9e4b05] >>> ACK
> >>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
> >>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
> >>> bytes=466
> >>>
> >>>
> >>> From: Ramu
> >>> Sent: Tuesday, April 14, 2009 12:58 PM
> >>> To: Joegen Baclor ; ope...@li...
> >>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
> >>>
> >>>
> >>> Hi,
> >>>
> >>> Thanks for your quick reply.
> >>>
> >>> I am here with attaching level 5 log files
> >>> 1) opensbc-invite-private-contact.zip file, it shows ACK problem (ACK
> is
> >>> going to private contact)
> >>> 2) opensbc-register.zip file, it shows REGISTER log file.
> >>>
> >>>
> >>>
> >>> On Tue, Apr 14, 2009 at 6:38 AM, Joegen Baclor <
> joe...@gm...>
> >>> wrote:
> >>>
> >>>  I don't get it.  ACK is a mid-dialog request and has nothing to do
> with
> >>> the
> >>>  Registration contact.  The registration contact would only be
> >>> significant
> >>>  when routing INVITE.   The fact that the call reaches the destination
> >>> UA
> >>>  proves that everything is in order as far as routing through the
> >>> registrar
> >>>  is concerned.   Please send an ethereal capture as well as the level 5
> >>> log
> >>>  of OpenSBC so we can see what is exactly happening to the ACK.
> >>>
> >>>  Joegen
> >>>
> >>>  --------------------------------------------------
> >>>
> >>>  From: "Ramu" <con...@gm...>
> >>>
> >>>  Sent: Tuesday, April 14, 2009 1:05 AM
> >>>
> >>>  To: <ope...@li...>
> >>>
> >>>  Subject: [OpenSIPStack] OpenSBC UpperRegistration Query
> >>>
> >>>
> >>>  > Hi,
> >>>  >
> >>>  > We are using OpenSBC in upper registration mode.
> >>>  >
> >>>  > When we register phones OpenSBC storing private contact (please see
> >>> the
> >>>  > attachment)
> >>>  >
> >>>  > As it is storing private contact when we try to make calls to
> >>> registered
> >>>  > user ACK is going to private contact which is not reaching phone.
> >>>  >
> >>>  > Please see full details of this problem in below thread.
> >>>  >
> >>>  > http://www.opensourcesip.org:8080/clearspacex/message/9442
> >>>  >
> >>>  > I appreciate your hep.
> >>>  >
> >>>  > Thanks,
> >>>  > Ramu
> >>>  >
> >>>
> >>>
> >>>
> >>>
> >>>  >
> >>>
> ------------------------------------------------------------------------------
> >>>  > This SF.net email is sponsored by:
> >>>  > High Quality Requirements in a Collaborative Environment.
> >>>  > Download a free trial of Rational Requirements Composer Now!
> >>>  > http://p.sf.net/sfu/www-ibm-com
> >>>
> >>>
> >>>
> >>>  > _______________________________________________
> >>>  > opensipstack-devel mailing list
> >>>
> >>>  > ope...@li...
> >>>
> >>>  > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
> >>>  >
> >>>
> >>>
> >>>
> >>>  >
> >>>  > No virus found in this incoming message.
> >>>  > Checked by AVG - www.avg.com
> >>>  > Version: 8.0.238 / Virus Database: 270.11.54/2055 - Release Date:
> >>> 04/12/09
> >>>  > 13:14:00
> >>>  >
> >>>
> >>>
> >>>
>  ------------------------------------------------------------------------------
> >>>  This SF.net email is sponsored by:
> >>>  High Quality Requirements in a Collaborative Environment.
> >>>  Download a free trial of Rational Requirements Composer Now!
> >>>  http://p.sf.net/sfu/www-ibm-com
> >>>  _______________________________________________
> >>>  opensipstack-devel mailing list
> >>>
> >>>  ope...@li...
> >>>
> >>>  https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> Ramu
> >>>
> >>>
> >>>
> >>>
> >>>
> --------------------------------------------------------------------------------
> >>>
> >>>
> >>>
> >>> No virus found in this incoming message.
> >>> Checked by AVG - www.avg.com
> >>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
> >>> 04/13/09
> >>> 17:56:00
> >>>
> >>>
> ------------------------------------------------------------------------------
> >>> This SF.net email is sponsored by:
> >>> High Quality Requirements in a Collaborative Environment.
> >>> Download a free trial of Rational Requirements Composer Now!
> >>> http://p.sf.net/sfu/www-ibm-com
> >>> _______________________________________________
> >>> opensipstack-devel mailing list
> >>> ope...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
> >>>
> >>
> >>
> >>
> >>
> >>> No virus found in this incoming message.
> >>> Checked by AVG - www.avg.com
> >>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
> >>> 04/13/09
> >>> 17:56:00
> >>>
> >>>
> >
> >
> > --
> > Ramu
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by:
> > High Quality Requirements in a Collaborative Environment.
> > Download a free trial of Rational Requirements Composer Now!
> > http://p.sf.net/sfu/www-ibm-com
> > _______________________________________________
> > opensipstack-devel mailing list
> > ope...@li...
> > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
> >
>
>
>
> >
> > No virus found in this incoming message.
> > Checked by AVG - www.avg.com
> > Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date:
> 04/13/09
> > 17:56:00
> >
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



-- 
Ramu

Re: [OpenSIPStack] OpenSBC UpperRegistration Query

[Joegen B. <joe...@gm...>]

I meant the OpenSIPStack library.  Not OpenSBC.  Are you using the latest 
library as well?

--------------------------------------------------
From: "Ramu" <con...@gm...>
Sent: Tuesday, April 14, 2009 2:42 PM
To: "Joegen Baclor" <jb...@so...>
Cc: <ope...@li...>
Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query

> Hi,
>
> Yes Am using latest version.  Following are my version details:
>
> [root@as1 distrib]# ./opensbc -v
> Product Name: OpenSBC
> Manufacturer: opensipstack.org
> Version     : 1.1.5-96
> System      : Linux-i686 2.6.18-92.1.18.el5.028stab060.2PAE
> Release-Date: Mar 30 2009 16:27:46
>
>
> On Tue, Apr 14, 2009 at 11:26 AM, Joegen Baclor 
> <joe...@gm...>wrote:
>
>> Ramu,
>>
>> By any chance, are you using the recent version of the OpenSIPStack 
>> library
>> as well?  There was a bug in record-routing in previous commits where the
>> port is not sepcified in the Record-Route.   It seems the log indicates 
>> that
>> you are suffering from this bug
>>
>> Joegen
>>
>> --------------------------------------------------
>> From: "Joegen Baclor" <joe...@gm...>
>> Sent: Tuesday, April 14, 2009 1:17 PM
>> To: "Ramu" <con...@gm...>; <
>> ope...@li...>
>>
>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>>
>>  I GREPed all the ACKs sent by opensbc from the log you sent.  Which 
>> among
>>> this ACK requests are getting sent to the the wrong destination (DST:)?
>>>
>>> 2009/04/02 15:45:59.029 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 59.93.81.139:55128:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=421
>>> 2009/04/02 15:45:59.035 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> bytes=466
>>> 2009/04/02 15:45:59.039 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=496
>>> 2009/04/02 15:45:59.540 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=496
>>> 2009/04/02 15:45:59.545 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> bytes=466
>>> 2009/04/02 15:46:00.041 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=496
>>> 2009/04/02 15:46:00.350 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> bytes=466
>>> 2009/04/02 15:46:01.045 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=496
>>> 2009/04/02 15:46:01.354 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> bytes=466
>>> 2009/04/02 15:46:03.054 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=496
>>> 2009/04/02 15:46:03.363 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> bytes=466
>>> 2009/04/02 15:46:03.557 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=496
>>> 2009/04/02 15:46:03.866 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> bytes=466
>>> 2009/04/02 15:46:04.060 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>>> bytes=496
>>> 2009/04/02 15:46:04.369 INF: [CID=0x9a9e4b05] >>> ACK
>>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>>> bytes=466
>>>
>>>
>>> From: Ramu
>>> Sent: Tuesday, April 14, 2009 12:58 PM
>>> To: Joegen Baclor ; ope...@li...
>>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>>>
>>>
>>> Hi,
>>>
>>> Thanks for your quick reply.
>>>
>>> I am here with attaching level 5 log files
>>> 1) opensbc-invite-private-contact.zip file, it shows ACK problem (ACK is
>>> going to private contact)
>>> 2) opensbc-register.zip file, it shows REGISTER log file.
>>>
>>>
>>>
>>> On Tue, Apr 14, 2009 at 6:38 AM, Joegen Baclor <joe...@gm...>
>>> wrote:
>>>
>>>  I don't get it.  ACK is a mid-dialog request and has nothing to do with
>>> the
>>>  Registration contact.  The registration contact would only be 
>>> significant
>>>  when routing INVITE.   The fact that the call reaches the destination 
>>> UA
>>>  proves that everything is in order as far as routing through the
>>> registrar
>>>  is concerned.   Please send an ethereal capture as well as the level 5
>>> log
>>>  of OpenSBC so we can see what is exactly happening to the ACK.
>>>
>>>  Joegen
>>>
>>>  --------------------------------------------------
>>>
>>>  From: "Ramu" <con...@gm...>
>>>
>>>  Sent: Tuesday, April 14, 2009 1:05 AM
>>>
>>>  To: <ope...@li...>
>>>
>>>  Subject: [OpenSIPStack] OpenSBC UpperRegistration Query
>>>
>>>
>>>  > Hi,
>>>  >
>>>  > We are using OpenSBC in upper registration mode.
>>>  >
>>>  > When we register phones OpenSBC storing private contact (please see 
>>> the
>>>  > attachment)
>>>  >
>>>  > As it is storing private contact when we try to make calls to
>>> registered
>>>  > user ACK is going to private contact which is not reaching phone.
>>>  >
>>>  > Please see full details of this problem in below thread.
>>>  >
>>>  > http://www.opensourcesip.org:8080/clearspacex/message/9442
>>>  >
>>>  > I appreciate your hep.
>>>  >
>>>  > Thanks,
>>>  > Ramu
>>>  >
>>>
>>>
>>>
>>>
>>>  >
>>> ------------------------------------------------------------------------------
>>>  > This SF.net email is sponsored by:
>>>  > High Quality Requirements in a Collaborative Environment.
>>>  > Download a free trial of Rational Requirements Composer Now!
>>>  > http://p.sf.net/sfu/www-ibm-com
>>>
>>>
>>>
>>>  > _______________________________________________
>>>  > opensipstack-devel mailing list
>>>
>>>  > ope...@li...
>>>
>>>  > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>  >
>>>
>>>
>>>
>>>  >
>>>  > No virus found in this incoming message.
>>>  > Checked by AVG - www.avg.com
>>>  > Version: 8.0.238 / Virus Database: 270.11.54/2055 - Release Date:
>>> 04/12/09
>>>  > 13:14:00
>>>  >
>>>
>>>
>>>  ------------------------------------------------------------------------------
>>>  This SF.net email is sponsored by:
>>>  High Quality Requirements in a Collaborative Environment.
>>>  Download a free trial of Rational Requirements Composer Now!
>>>  http://p.sf.net/sfu/www-ibm-com
>>>  _______________________________________________
>>>  opensipstack-devel mailing list
>>>
>>>  ope...@li...
>>>
>>>  https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>>
>>>
>>>
>>> --
>>> Ramu
>>>
>>>
>>>
>>>
>>> --------------------------------------------------------------------------------
>>>
>>>
>>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 
>>> 04/13/09
>>> 17:56:00
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by:
>>> High Quality Requirements in a Collaborative Environment.
>>> Download a free trial of Rational Requirements Composer Now!
>>> http://p.sf.net/sfu/www-ibm-com
>>> _______________________________________________
>>> opensipstack-devel mailing list
>>> ope...@li...
>>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>>
>>
>>
>>
>>
>>> No virus found in this incoming message.
>>> Checked by AVG - www.avg.com
>>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 
>>> 04/13/09
>>> 17:56:00
>>>
>>>
>
>
> -- 
> Ramu
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 04/13/09 
> 17:56:00
> 

Re: [OpenSIPStack] OpenSBC UpperRegistration Query

[Ramu <con...@gm...>]

Hi,

Yes Am using latest version.  Following are my version details:

[root@as1 distrib]# ./opensbc -v
Product Name: OpenSBC
Manufacturer: opensipstack.org
Version     : 1.1.5-96
System      : Linux-i686 2.6.18-92.1.18.el5.028stab060.2PAE
Release-Date: Mar 30 2009 16:27:46


On Tue, Apr 14, 2009 at 11:26 AM, Joegen Baclor <joe...@gm...>wrote:

> Ramu,
>
> By any chance, are you using the recent version of the OpenSIPStack library
> as well?  There was a bug in record-routing in previous commits where the
> port is not sepcified in the Record-Route.   It seems the log indicates that
> you are suffering from this bug
>
> Joegen
>
> --------------------------------------------------
> From: "Joegen Baclor" <joe...@gm...>
> Sent: Tuesday, April 14, 2009 1:17 PM
> To: "Ramu" <con...@gm...>; <
> ope...@li...>
>
> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>
>  I GREPed all the ACKs sent by opensbc from the log you sent.  Which among
>> this ACK requests are getting sent to the the wrong destination (DST:)?
>>
>> 2009/04/02 15:45:59.029 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 59.93.81.139:55128:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=421
>> 2009/04/02 15:45:59.035 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> bytes=466
>> 2009/04/02 15:45:59.039 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=496
>> 2009/04/02 15:45:59.540 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=496
>> 2009/04/02 15:45:59.545 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> bytes=466
>> 2009/04/02 15:46:00.041 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=496
>> 2009/04/02 15:46:00.350 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> bytes=466
>> 2009/04/02 15:46:01.045 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=496
>> 2009/04/02 15:46:01.354 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> bytes=466
>> 2009/04/02 15:46:03.054 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=496
>> 2009/04/02 15:46:03.363 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> bytes=466
>> 2009/04/02 15:46:03.557 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=496
>> 2009/04/02 15:46:03.866 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> bytes=466
>> 2009/04/02 15:46:04.060 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0
>> bytes=496
>> 2009/04/02 15:46:04.369 INF: [CID=0x9a9e4b05] >>> ACK
>> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0
>> Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0
>> bytes=466
>>
>>
>> From: Ramu
>> Sent: Tuesday, April 14, 2009 12:58 PM
>> To: Joegen Baclor ; ope...@li...
>> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>>
>>
>> Hi,
>>
>> Thanks for your quick reply.
>>
>> I am here with attaching level 5 log files
>> 1) opensbc-invite-private-contact.zip file, it shows ACK problem (ACK is
>> going to private contact)
>> 2) opensbc-register.zip file, it shows REGISTER log file.
>>
>>
>>
>> On Tue, Apr 14, 2009 at 6:38 AM, Joegen Baclor <joe...@gm...>
>> wrote:
>>
>>  I don't get it.  ACK is a mid-dialog request and has nothing to do with
>> the
>>  Registration contact.  The registration contact would only be significant
>>  when routing INVITE.   The fact that the call reaches the destination UA
>>  proves that everything is in order as far as routing through the
>> registrar
>>  is concerned.   Please send an ethereal capture as well as the level 5
>> log
>>  of OpenSBC so we can see what is exactly happening to the ACK.
>>
>>  Joegen
>>
>>  --------------------------------------------------
>>
>>  From: "Ramu" <con...@gm...>
>>
>>  Sent: Tuesday, April 14, 2009 1:05 AM
>>
>>  To: <ope...@li...>
>>
>>  Subject: [OpenSIPStack] OpenSBC UpperRegistration Query
>>
>>
>>  > Hi,
>>  >
>>  > We are using OpenSBC in upper registration mode.
>>  >
>>  > When we register phones OpenSBC storing private contact (please see the
>>  > attachment)
>>  >
>>  > As it is storing private contact when we try to make calls to
>> registered
>>  > user ACK is going to private contact which is not reaching phone.
>>  >
>>  > Please see full details of this problem in below thread.
>>  >
>>  > http://www.opensourcesip.org:8080/clearspacex/message/9442
>>  >
>>  > I appreciate your hep.
>>  >
>>  > Thanks,
>>  > Ramu
>>  >
>>
>>
>>
>>
>>  >
>> ------------------------------------------------------------------------------
>>  > This SF.net email is sponsored by:
>>  > High Quality Requirements in a Collaborative Environment.
>>  > Download a free trial of Rational Requirements Composer Now!
>>  > http://p.sf.net/sfu/www-ibm-com
>>
>>
>>
>>  > _______________________________________________
>>  > opensipstack-devel mailing list
>>
>>  > ope...@li...
>>
>>  > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>  >
>>
>>
>>
>>  >
>>  > No virus found in this incoming message.
>>  > Checked by AVG - www.avg.com
>>  > Version: 8.0.238 / Virus Database: 270.11.54/2055 - Release Date:
>> 04/12/09
>>  > 13:14:00
>>  >
>>
>>
>>  ------------------------------------------------------------------------------
>>  This SF.net email is sponsored by:
>>  High Quality Requirements in a Collaborative Environment.
>>  Download a free trial of Rational Requirements Composer Now!
>>  http://p.sf.net/sfu/www-ibm-com
>>  _______________________________________________
>>  opensipstack-devel mailing list
>>
>>  ope...@li...
>>
>>  https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>>
>>
>>
>> --
>> Ramu
>>
>>
>>
>>
>> --------------------------------------------------------------------------------
>>
>>
>>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 04/13/09
>> 17:56:00
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by:
>> High Quality Requirements in a Collaborative Environment.
>> Download a free trial of Rational Requirements Composer Now!
>> http://p.sf.net/sfu/www-ibm-com
>> _______________________________________________
>> opensipstack-devel mailing list
>> ope...@li...
>> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>>
>
>
>
>
>> No virus found in this incoming message.
>> Checked by AVG - www.avg.com
>> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 04/13/09
>> 17:56:00
>>
>>


-- 
Ramu

Re: [OpenSIPStack] OpenSBC UpperRegistration Query

[Joegen B. <joe...@gm...>]

Ramu,

By any chance, are you using the recent version of the OpenSIPStack library 
as well?  There was a bug in record-routing in previous commits where the 
port is not sepcified in the Record-Route.   It seems the log indicates that 
you are suffering from this bug

Joegen

--------------------------------------------------
From: "Joegen Baclor" <joe...@gm...>
Sent: Tuesday, April 14, 2009 1:17 PM
To: "Ramu" <con...@gm...>; 
<ope...@li...>
Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query

> I GREPed all the ACKs sent by opensbc from the log you sent.  Which among 
> this ACK requests are getting sent to the the wrong destination (DST:)?
>
> 2009/04/02 15:45:59.029 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 59.93.81.139:55128:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=421
> 2009/04/02 15:45:59.035 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
> 2009/04/02 15:45:59.039 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
> 2009/04/02 15:45:59.540 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
> 2009/04/02 15:45:59.545 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
> 2009/04/02 15:46:00.041 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
> 2009/04/02 15:46:00.350 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
> 2009/04/02 15:46:01.045 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
> 2009/04/02 15:46:01.354 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
> 2009/04/02 15:46:03.054 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
> 2009/04/02 15:46:03.363 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
> 2009/04/02 15:46:03.557 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
> 2009/04/02 15:46:03.866 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
> 2009/04/02 15:46:04.060 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
> 2009/04/02 15:46:04.369 INF: [CID=0x9a9e4b05] >>> ACK 
> sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) 
> DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
>
>
> From: Ramu
> Sent: Tuesday, April 14, 2009 12:58 PM
> To: Joegen Baclor ; ope...@li...
> Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query
>
>
> Hi,
>
> Thanks for your quick reply.
>
> I am here with attaching level 5 log files
> 1) opensbc-invite-private-contact.zip file, it shows ACK problem (ACK is 
> going to private contact)
> 2) opensbc-register.zip file, it shows REGISTER log file.
>
>
>
> On Tue, Apr 14, 2009 at 6:38 AM, Joegen Baclor <joe...@gm...> 
> wrote:
>
>  I don't get it.  ACK is a mid-dialog request and has nothing to do with 
> the
>  Registration contact.  The registration contact would only be significant
>  when routing INVITE.   The fact that the call reaches the destination UA
>  proves that everything is in order as far as routing through the 
> registrar
>  is concerned.   Please send an ethereal capture as well as the level 5 
> log
>  of OpenSBC so we can see what is exactly happening to the ACK.
>
>  Joegen
>
>  --------------------------------------------------
>
>  From: "Ramu" <con...@gm...>
>
>  Sent: Tuesday, April 14, 2009 1:05 AM
>
>  To: <ope...@li...>
>
>  Subject: [OpenSIPStack] OpenSBC UpperRegistration Query
>
>
>  > Hi,
>  >
>  > We are using OpenSBC in upper registration mode.
>  >
>  > When we register phones OpenSBC storing private contact (please see the
>  > attachment)
>  >
>  > As it is storing private contact when we try to make calls to 
> registered
>  > user ACK is going to private contact which is not reaching phone.
>  >
>  > Please see full details of this problem in below thread.
>  >
>  > http://www.opensourcesip.org:8080/clearspacex/message/9442
>  >
>  > I appreciate your hep.
>  >
>  > Thanks,
>  > Ramu
>  >
>
>
>
>
>  > ------------------------------------------------------------------------------
>  > This SF.net email is sponsored by:
>  > High Quality Requirements in a Collaborative Environment.
>  > Download a free trial of Rational Requirements Composer Now!
>  > http://p.sf.net/sfu/www-ibm-com
>
>
>
>  > _______________________________________________
>  > opensipstack-devel mailing list
>
>  > ope...@li...
>
>  > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>  >
>
>
>
>  >
>  > No virus found in this incoming message.
>  > Checked by AVG - www.avg.com
>  > Version: 8.0.238 / Virus Database: 270.11.54/2055 - Release Date: 
> 04/12/09
>  > 13:14:00
>  >
>
>  ------------------------------------------------------------------------------
>  This SF.net email is sponsored by:
>  High Quality Requirements in a Collaborative Environment.
>  Download a free trial of Rational Requirements Composer Now!
>  http://p.sf.net/sfu/www-ibm-com
>  _______________________________________________
>  opensipstack-devel mailing list
>
>  ope...@li...
>
>  https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>
>
> -- 
> Ramu
>
>
>
> --------------------------------------------------------------------------------
>
>
>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 04/13/09 
> 17:56:00
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> High Quality Requirements in a Collaborative Environment.
> Download a free trial of Rational Requirements Composer Now!
> http://p.sf.net/sfu/www-ibm-com
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel



>
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 04/13/09 
> 17:56:00
> 

Re: [OpenSIPStack] OpenSBC UpperRegistration Query

[Joegen B. <joe...@gm...>]

I GREPed all the ACKs sent by opensbc from the log you sent.  Which among this ACK requests are getting sent to the the wrong destination (DST:)?

2009/04/02 15:45:59.029 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 59.93.81.139:55128:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=421
2009/04/02 15:45:59.035 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
2009/04/02 15:45:59.039 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
2009/04/02 15:45:59.540 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
2009/04/02 15:45:59.545 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
2009/04/02 15:46:00.041 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
2009/04/02 15:46:00.350 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
2009/04/02 15:46:01.045 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
2009/04/02 15:46:01.354 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
2009/04/02 15:46:03.054 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
2009/04/02 15:46:03.363 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
2009/04/02 15:46:03.557 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
2009/04/02 15:46:03.866 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466
2009/04/02 15:46:04.060 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5070:UDP  SRC: 66.42.9.197:6060 enc=0 bytes=496
2009/04/02 15:46:04.369 INF: [CID=0x9a9e4b05] >>> ACK sip:2000@59.93.81.139:55128;rinstance=67ffc600210dc67d SIP/2.0 Method(ACK) DST: 66.42.9.197:5060:UDP  SRC: 66.42.9.197:5062 enc=0 bytes=466


From: Ramu 
Sent: Tuesday, April 14, 2009 12:58 PM
To: Joegen Baclor ; ope...@li... 
Subject: Re: [OpenSIPStack] OpenSBC UpperRegistration Query


Hi,

Thanks for your quick reply.

I am here with attaching level 5 log files
1) opensbc-invite-private-contact.zip file, it shows ACK problem (ACK is going to private contact)
2) opensbc-register.zip file, it shows REGISTER log file.



On Tue, Apr 14, 2009 at 6:38 AM, Joegen Baclor <joe...@gm...> wrote:

  I don't get it.  ACK is a mid-dialog request and has nothing to do with the
  Registration contact.  The registration contact would only be significant
  when routing INVITE.   The fact that the call reaches the destination UA
  proves that everything is in order as far as routing through the registrar
  is concerned.   Please send an ethereal capture as well as the level 5 log
  of OpenSBC so we can see what is exactly happening to the ACK.

  Joegen

  --------------------------------------------------

  From: "Ramu" <con...@gm...>

  Sent: Tuesday, April 14, 2009 1:05 AM

  To: <ope...@li...>

  Subject: [OpenSIPStack] OpenSBC UpperRegistration Query


  > Hi,
  >
  > We are using OpenSBC in upper registration mode.
  >
  > When we register phones OpenSBC storing private contact (please see the
  > attachment)
  >
  > As it is storing private contact when we try to make calls to registered
  > user ACK is going to private contact which is not reaching phone.
  >
  > Please see full details of this problem in below thread.
  >
  > http://www.opensourcesip.org:8080/clearspacex/message/9442
  >
  > I appreciate your hep.
  >
  > Thanks,
  > Ramu
  >




  > ------------------------------------------------------------------------------
  > This SF.net email is sponsored by:
  > High Quality Requirements in a Collaborative Environment.
  > Download a free trial of Rational Requirements Composer Now!
  > http://p.sf.net/sfu/www-ibm-com



  > _______________________________________________
  > opensipstack-devel mailing list

  > ope...@li...

  > https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
  >



  >
  > No virus found in this incoming message.
  > Checked by AVG - www.avg.com
  > Version: 8.0.238 / Virus Database: 270.11.54/2055 - Release Date: 04/12/09
  > 13:14:00
  >

  ------------------------------------------------------------------------------
  This SF.net email is sponsored by:
  High Quality Requirements in a Collaborative Environment.
  Download a free trial of Rational Requirements Composer Now!
  http://p.sf.net/sfu/www-ibm-com
  _______________________________________________
  opensipstack-devel mailing list

  ope...@li...

  https://lists.sourceforge.net/lists/listinfo/opensipstack-devel




-- 
Ramu



--------------------------------------------------------------------------------



No virus found in this incoming message.
Checked by AVG - www.avg.com 
Version: 8.0.238 / Virus Database: 270.11.55/2057 - Release Date: 04/13/09 17:56:00