NOTIFY BLF

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

NOTIFY BLF

Slava Bendersky-2
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: <sip:[hidden email]:5160>;tag=054Zqq8YyZTA
To: "45201" <sip:[hidden email]:5160>;tag=1948650230
Call-ID: 0_1579912862@192.168.1.32
CSeq: 306302851 NOTIFY
Contact: <sip:45200@10.100.104.12:5160;transport=tcp>
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

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="13" state="full" entity="sip:[hidden email]">
<dialog id="59fc03ba-36f5-4c1c-8a18-f0ac6e81316a" direction="initiator">
<state>confirmed</state>
<local>
<identity display="45200">sip:[hidden email]</identity>
<target uri="sip:[hidden email]">
<param pname="+sip.rendering" pvalue="yes"/>
</target>
</local>
<remote>
<identity display="*97">sip:*[hidden email]</identity>
<target uri="sip:**[hidden email]"/>
</remote>
</dialog>
</dialog-info>


volga629

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: NOTIFY BLF

Bogdan-Andrei Iancu-2
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 <a class="moz-txt-link-freetext" href="sip:45201@47.185.53.190:12428;nat=yes;transport=TCP">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: <a class="moz-txt-link-rfc2396E" href="sip:45200@dev.ait.local:5160"><sip:45200@...:5160>;tag=054Zqq8YyZTA
To: "45201" <a class="moz-txt-link-rfc2396E" href="sip:45201@dev.ait.local:5160"><sip:45201@...:5160>;tag=1948650230
CSeq: 306302851 NOTIFY
Contact: <a class="moz-txt-link-rfc2396E" href="sip:45200@10.100.104.12:5160;transport=tcp"><sip:45200@10.100.104.12:5160;transport=tcp>
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

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="13" state="full" entity=<a class="moz-txt-link-rfc2396E" href="sip:45200@dev.ait.local">"sip:45200@...">
<dialog id="59fc03ba-36f5-4c1c-8a18-f0ac6e81316a" direction="initiator">
<state>confirmed</state>
<local>
<identity display="45200"><a class="moz-txt-link-freetext" href="sip:45200@dev.ait.local">sip:45200@...</identity>
<target uri=<a class="moz-txt-link-rfc2396E" href="sip:45200@dev.ait.local">"sip:45200@...">
<param pname="+sip.rendering" pvalue="yes"/>
</target>
</local>
<remote>
<identity display="*97"><a class="moz-txt-link-freetext" href="sip:*97@dev.ait.local">sip:*97@...</identity>
<target uri=<a class="moz-txt-link-rfc2396E" href="sip:**45200@dev.ait.local">"sip:**45200@..."/>
</remote>
</dialog>
</dialog-info>


volga629


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: NOTIFY BLF

Bogdan-Andrei Iancu-2
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" [hidden email]
To: "Slava Bendersky" [hidden email], [hidden email]
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
Via: SIP/2.0/UDP 10.100.104.12:5160;rport;branch=z9hG4bKjDtU5Zt1ey70a
Max-Forwards: 70
From: <sip:[hidden email]:5160>;tag=054Zqq8YyZTA
To: "45201" <sip:[hidden email]:5160>;tag=1948650230
CSeq: 306302851 NOTIFY
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

<?xml version="1.0"?>
<dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="13" state="full" entity="sip:[hidden email]">
<dialog id="59fc03ba-36f5-4c1c-8a18-f0ac6e81316a" direction="initiator">
<state>confirmed</state>
<local>
<identity display="45200">sip:[hidden email]</identity>
<target uri="sip:[hidden email]">
<param pname="+sip.rendering" pvalue="yes"/>
</target>
</local>
<remote>
<identity display="*97">sip:*[hidden email]</identity>
<target uri="sip:**[hidden email]"/>
</remote>
</dialog>
</dialog-info>


volga629


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users



_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users