reSIProcate

Mailing Lists

Source Code

Google Search:



< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

Re: [reSIProcate-users] Does the reSIProcate support BroadSoft "Remote Control Talk Event Package" ?

In this case it looks like the Notifies are in-dialog (INVITE dialog), so I don't think that will work.

Scott

On Tue, Nov 23, 2010 at 12:30 PM, Jim Hodsdon <jim.hodsdon@xxxxxxxxxx> wrote:

I’ve handled similar “unsolicited” Notify’s through DUM’s OutOfDialogHandler.

 

Jim H.

 


This email communication may contain CONFIDENTIAL, PRIVILEGED and/or
LEGALLY PROTECTED information and is intended only for the named
recipient(s). Any unauthorized use, dissemination, copying or forwarding
is strictly prohibited. If you are not the intended recipient and have
received this email communication in error, please notify the sender
immediately, delete it and destroy all copies of this email.

From: resiprocate-users-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Scott Godin
Sent: Tuesday, November 23, 2010 11:23 AM


To: Kennard White
Cc: resiprocate-users@xxxxxxxxxxxxxxx
Subject: Re: [reSIProcate-users] Does the reSIProcate support BroadSoft "Remote Control Talk Event Package" ?

 

Took a quick look at the broadsoft doc (http://track.sipfoundry.org/secure/attachment/17372/BW-SIPAccessSideExtensionsInterfaceSpec-R1301.pdf) - this "talk" event package is not really implemented following all the rules in RFC3265 - there is no explicit subscribe request, and the notifies are unsolicited within the INIVTE dialog.  You would need to modify DUM in order to support this.

 

Scott

On Tue, Nov 23, 2010 at 11:53 AM, Kennard White <kennard_white@xxxxxxxxxxxx> wrote:

Hi Karlsson,

I'm not that familiar with the dum layer, so hopefully someone else can confirm or correct this. As far as I know, the "custom" event handlers apply to explicit SUBSCRIBE dialogs. Based upon looking at Dialog.cxx, the only NOTIFY event handled within INVITE dialogs is "refer".

What to have happen when the stack(dum) gets one of these NOTIFY events? Is there an RFC (or equiv) that specifies these event messages?

Regards,
Kennard

On Mon, Nov 22, 2010 at 10:01 PM, Karlsson <boost.regex@xxxxxxxxx> wrote:

Hi all, when I run my APP with a SIP server which is support BroadSoft "Remote Control Talk Event Package" , the reSIProcate rejected the NOTIFY message automatically.

the flow is:

1. My APP received the INVITE from server
2. My APP send the 180 RINGRING message to server with a header: ALLOW-EVENTS:hold, talk
3. Server send a NOTIFY message to My APP, this NOTIFY included a header: Event:talk

Now the problem is reSIProcate rejected this NOTIFY automatically by 406, how to let the resiprocate accept this NOTIFY?

I have added the hander:

static const Data customEvent("talk");
mDum.addClientSubscriptionHandler(customEvent, this);
mDum.addServerSubscriptionHandler(customEvent, this);


Here is the log:


NOTIFY sip:61208@xxxxxxxx:5162;rinstance=bb656e5ff7cad056 SIP/2.0
Via: SIP/2.0/UDP 10.X.X.X:5060;branch=z9hG4bK69DC2814-092E-42E0-967B-2436EC73519E-10811228
Max-Forwards: 69
Contact: <sip:2626791809@xxxxxxxx:5060>
To: "TEST"<sip:61208@xxxxxxxx>;tag=3476a309
From: "TEST" <sip:2626791809@xxxxxxxx>;tag=82AF9975-A094-4515-819B-D4842310020B-4254516
Call-ID: 87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxx
CSeq: 2 NOTIFY
Subscription-State: active
Event: talk
Content-Length: 0


INFO | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:1335 | Got: SipReq:  NOTIFY 61208@xxxxxxxx:5162 tid=69DC2814-092E-42E0-967B-2436EC73519E-10811228 cseq=NOTIFY contact=2626791809@xxxxxxxx:5060 / 2 from(wire)
DEBUG | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:1653 | DialogUsageManager::processRequest: SipReq:  NOTIFY 61208@xxxxxxxx:5162 tid=69DC2814-092E-42E0-967B-2436EC73519E-10811228 cseq=NOTIFY contact=2626791809@xxxxxxxx:5060 / 2 from(wire)
STACK | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:1959 | Looking for dialogSet: 87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxxxxxxxxxxx in map:
STACK | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:1960 | [87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxxxxxxxxxxx -> 0DA91A10, MDkxMTEyYTJhZDMyYzk2ZGM4NjhmMmJjODJhY2M0Yjg.-f3505015 -> 0DA8E730]
INFO | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:1713 | Handling in-dialog request: SipReq:  NOTIFY 61208@xxxxxxxx:5162 tid=69DC2814-092E-42E0-967B-2436EC73519E-10811228 cseq=NOTIFY contact=2626791809@xxxxxxxx:5060 / 2 from(wire)
DEBUG | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogId.cxx:50 | DialogId::DialogId: 87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
DEBUG | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogSet.cxx:530 | Found matching dialog mClientSubscriptions(0), mServerSubscriptions(0) for

NOTIFY sip:61208@xxxxxxxx:5162;rinstance=bb656e5ff7cad056 SIP/2.0
Via: SIP/2.0/UDP 10.X.X.X:5060;branch=z9hG4bK69DC2814-092E-42E0-967B-2436EC73519E-10811228
Max-Forwards: 69
Contact: <sip:2626791809@xxxxxxxx:5060>
To: "TEST"<sip:61208@xxxxxxxx>;tag=3476a309
From: "TEST"<sip:2626791809@xxxxxxxx>;tag=82AF9975-A094-4515-819B-D4842310020B-4254516
Call-ID: 87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxx
CSeq: 2 NOTIFY
Subscription-State: active
Event: talk
Content-Length: 0


DEBUG | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | Dialog.cxx:370 | Dialog::dispatch: SipReq:  NOTIFY 61208@xxxxxxxx:5162 tid=69DC2814-092E-42E0-967B-2436EC73519E-10811228 cseq=NOTIFY contact=2626791809@xxxxxxxx:5060 / 2 from(wire)
DEBUG | 20101122-161420.608 | My APP | RESIP | 6868 | Helper.cxx:375 | Helper::makeResponse(SipReq:  NOTIFY 61208@xxxxxxxx:5162 tid=69DC2814-092E-42E0-967B-2436EC73519E-10811228 cseq=NOTIFY contact=2626791809@xxxxxxxx:5060 / 2 from(wire) code=406 reason=
DEBUG | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | Dialog.cxx:1076 | Dialog::makeResponse:

SIP/2.0 406 Not Acceptable
Via: SIP/2.0/UDP 10.X.X.X:5060;branch=z9hG4bK69DC2814-092E-42E0-967B-2436EC73519E-10811228
To: "TEST"<sip:61208@xxxxxxxx>;tag=3476a309
From: "TEST"<sip:2626791809@xxxxxxxx>;tag=82AF9975-A094-4515-819B-D4842310020B-4254516
Call-ID: 87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxx
CSeq: 2 NOTIFY
Content-Length: 0


STACK | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:1959 | Looking for dialogSet: 87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxxxxxxxxxxx in map:
STACK | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:1960 | [87E28076-A61F-4999-9F8D-C698014B556A-2693776@xxxxxxxxxxxxxxxxx -> 0DA91A10, MDkxMTEyYTJhZDMyYzk2ZGM4NjhmMmJjODJhY2M0Yjg.-f3505015 -> 0DA8E730]
DEBUG | 20101122-161420.608 | My APP | RESIP:DUM | 6868 | DialogUsageManager.cxx:867 | SEND:

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/



_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

 


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/