Re: [OpenSIPS-Users] NOTIFY BLF

2019-03-13 Thread Bogdan-Andrei Iancu

Great !

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 03/13/2019 02:30 PM, Slava Bendersky wrote:

Hello Bogdan,
Issue has being resolved.
NOTIFY is routed properly right now. Thank you for insight

if (loose_route()) {
if(is_method("REFER")) {
# Fix contact for REFER in dialog
route(HANDLE_NAT_FIX);
}

# BYE rtpengine_delete()
route(RTP_MANAGE);

route(RELAY);
exit;
} else {
if(is_method("NOTIFY")) {
xlog("L_INFO", "[$rm] Sending to client\n");
t_relay();
exit;
}


volga629


*From: *"Bogdan-Andrei Iancu" 
*To: *"Slava Bendersky" , users@lists.opensips.org
*Sent: *Wednesday, March 13, 2019 4:46:30 AM
*Subject: *Re: [OpenSIPS-Users] NOTIFY BLF

Hi Slava,

I see this is a sequential NOTIFY, so probably part of a SUBSCRIBE'ing 
session. If so, you need to route it as a generic sequential request 
via loose_route() + t_relay().


Does the SUBSCRIBE go via your OpenSIPS ? do you do record_route() for 
it ?


Regards,
Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
   https://www.opensips-solutions.com
OpenSIPS Summit 2019
   https://www.opensips.org/events/Summit-2019Amsterdam/
On 03/13/2019 05:24 AM, Slava Bendersky wrote:

Hello Everyone,
Having some trouble to handle NOTIFY for BLF send by Freeswitch to
opensips.
How I should handle it ? Do I need t_relay to the client ?


2019/03/12 21:40:57.281140 10.100.104.12:5160 -> 10.100.104.7:5060
NOTIFY sip:45201@47.185.53.190:12428;nat=yes;transport=TCP SIP/2.0
Via: SIP/2.0/UDP 10.100.104.12:5160;rport;branch=z9hG4bKjDtU5Zt1ey70a
Max-Forwards: 70
From: ;tag=054Zqq8YyZTA
To: "45201" ;tag=1948650230
Call-ID: 0_1579912862@192.168.1.32
CSeq: 306302851 NOTIFY
Contact: 
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE,
REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, path, replaces
Event: dialog
Allow-Events: talk, hold, conference, presence, as-feature-event,
dialog, line-seize, call-info, sla, include-session-description,
presence.winfo, message-summary, refer
Subscription-State: active;expires=530
Content-Type: application/dialog-info+xml
Content-Length: 551




confirmed

sip:45...@dev.ait.local





sip:*9...@dev.ait.local






volga629


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users




___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


Re: [OpenSIPS-Users] NOTIFY BLF

2019-03-13 Thread Bogdan-Andrei Iancu

Hi Slava,

I see this is a sequential NOTIFY, so probably part of a SUBSCRIBE'ing 
session. If so, you need to route it as a generic sequential request via 
loose_route() + t_relay().


Does the SUBSCRIBE go via your OpenSIPS ? do you do record_route() for it ?

Regards,

Bogdan-Andrei Iancu

OpenSIPS Founder and Developer
  https://www.opensips-solutions.com
OpenSIPS Summit 2019
  https://www.opensips.org/events/Summit-2019Amsterdam/

On 03/13/2019 05:24 AM, Slava Bendersky wrote:

Hello Everyone,
Having some trouble to handle NOTIFY for BLF send by Freeswitch to 
opensips.

How I should handle it ? Do I need t_relay to the client ?


2019/03/12 21:40:57.281140 10.100.104.12:5160 -> 10.100.104.7:5060
NOTIFY sip:45201@47.185.53.190:12428;nat=yes;transport=TCP SIP/2.0
Via: SIP/2.0/UDP 10.100.104.12:5160;rport;branch=z9hG4bKjDtU5Zt1ey70a
Max-Forwards: 70
From: ;tag=054Zqq8YyZTA
To: "45201" ;tag=1948650230
Call-ID: 0_1579912862@192.168.1.32
CSeq: 306302851 NOTIFY
Contact: 
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, 
REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE

Supported: timer, path, replaces
Event: dialog
Allow-Events: talk, hold, conference, presence, as-feature-event, 
dialog, line-seize, call-info, sla, include-session-description, 
presence.winfo, message-summary, refer

Subscription-State: active;expires=530
Content-Type: application/dialog-info+xml
Content-Length: 551


state="full" entity="sip:45...@dev.ait.local">


confirmed

sip:45...@dev.ait.local





sip:*9...@dev.ait.local






volga629


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users