5 May
2012
5 May
'12
4:15 p.m.
On anything newer than 1.06 of freeswitch the SIP NOTIFY sent to an Avaya
9630 phone does not get accepted and trigger the MWI light. Works
absolutely fine on 1.0.6.
The only difference in the messages i can see is in the contact parameter,
possibly to do with the angle bracket. Can anyone advise if the difference
shown in the two messages below is acceptable SIP or if something is broken
in freeswitch. Also, I'm happy to plough through code and try to fix if you
can point me in the right direction as to which src file constructs the SIP
Notify message ?
WORKING VERSION 1.0.6
No. Time Source Destination Protocol
Length Info
1169 19:32:47 192.168.2.41 192.168.2.30 SIP
996 Request: NOTIFY sip:1001@192.168.2.30;transport=udp
Frame 1169: 996 bytes on wire (7968 bits), 996 bytes captured (7968 bits)
Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst:
Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f)
Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst:
192.168.2.30 (192.168.2.30)
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)
Session Initiation Protocol
Request-Line: NOTIFY sip:1001@192.168.2.30;transport=udp SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKQ656yDjS3mavS
Transport: UDP
Sent-by Address: 192.168.2.41
RPort: rport
Branch: z9hG4bKQ656yDjS3mavS
Max-Forwards: 70
From: <sip:1001@192.168.2.41>;tag=eQH9S8pjtvp6N
To: <sip:1001@192.168.2.41
>;tag=286229214fa041cb4fa80fb2_F1001192.168.2.30
Call-ID: 1_7c8e554c7b5cb4fa80abf_S@192.168.2.30
CSeq: 27613481 NOTIFY
Sequence Number: 27613481
Method: NOTIFY
* Contact: <sip:1001@192.168.2.41:5060>*
User-Agent: FreeSWITCH-mod_sofia/1.0.6-hacked-20120317T221523Z
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO,
REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, precondition, path, replaces
Event: message-summary
Allow-Events: talk, presence, dialog, line-seize, call-info, sla,
include-session-description, presence.winfo, message-summary, refer
Subscription-State: active;expires=21
Content-Type: application/simple-message-summary
Content-Length: 91
Message Body
Messages-Waiting: yes\r\n
Message-Account: sip:1001@192.168.2.41\r\n
Voice-Message: 1/0 (0/0)\r\n
\r\n
BROKEN VERSION LATEST GIT
No. Time Source Destination Protocol
Length Info
6824 18:33:12 192.168.2.41 192.168.2.30 SIP
1034 Request: NOTIFY sip:1001@192.168.2.30;transport=udp
Frame 6824: 1034 bytes on wire (8272 bits), 1034 bytes captured (8272 bits)
Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst:
Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f)
Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst:
192.168.2.30 (192.168.2.30)
User Datagram Protocol, Src Port: sip (5060), Dst Port: iad2 (1031)
Session Initiation Protocol
Request-Line: NOTIFY sip:1001@192.168.2.30;transport=udp SIP/2.0
Message Header
Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKyyreB17m4eS1c
Transport: UDP
Sent-by Address: 192.168.2.41
RPort: rport
Branch: z9hG4bKyyreB17m4eS1c
Max-Forwards: 70
From: <sip:1001@192.168.2.41>;tag=Oa5sgbB1o7sl
SIP from address: sip:1001@192.168.2.41
SIP tag: Oa5sgbB1o7sl
To: <sip:1001@192.168.2.41
>;tag=2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30
SIP to address: sip:1001@192.168.2.41
SIP to address User Part: 1001
SIP to address Host Part: 192.168.2.41
SIP tag: 2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30
Call-ID: 7_2c27465e595004fa2f77c_S@192.168.2.30
CSeq: 231978492 NOTIFY
Sequence Number: 231978492
Method: NOTIFY
* Contact: <sip:1001@192.168.2.41:5060;transport=udp>
Contact-URI: sip:1001@192.168.2.41:5060;transport=udp
Contactt-URI User Part: 1001
Contact-URI Host Part: 192.168.2.41
Contact-URI Host Port: 5060
Contact parameter: transport=udp>*
User-Agent: FreeSWITCH-mod_sofia/1.1.beta1-git-de019ab 2012-05-03
15-23-57 +0200
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO,
REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: timer, precondition, path, replaces
Event: message-summary
Allow-Events: talk, hold, presence, dialog, line-seize, call-info,
sla, include-session-description, presence.winfo, message-summary, refer
Subscription-State: active;expires=60
Content-Type: application/simple-message-summary
Content-Length: 91
Message Body
Messages-Waiting: yes\r\n
Message-Account: sip:1001@192.168.2.41\r\n
Voice-Message: 2/0 (0/0)\r\n
\r\n
thanks as ever !
Bernie
5 May
5 May
9:19 p.m.
What do you have it set for contact-params in your sip profile? -djbinter On Sat, May 5, 2012 at 9:15 AM, Bernard Murphy < bernard.david.murphy@gmail.com> wrote: > On anything newer than 1.06 of freeswitch the SIP NOTIFY sent to an Avaya > 9630 phone does not get accepted and trigger the MWI light. Works > absolutely fine on 1.0.6. > > The only difference in the messages i can see is in the contact parameter, > possibly to do with the angle bracket. Can anyone advise if the difference > shown in the two messages below is acceptable SIP or if something is broken > in freeswitch. Also, I'm happy to plough through code and try to fix if you > can point me in the right direction as to which src file constructs the SIP > Notify message ? > > WORKING VERSION 1.0.6 > No. Time Source Destination Protocol > Length Info > 1169 19:32:47 192.168.2.41 192.168.2.30 SIP > 996 Request: NOTIFY sip:1001@192.168.2.30;transport=udp > > Frame 1169: 996 bytes on wire (7968 bits), 996 bytes captured (7968 bits) > Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst: > Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f) > Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst: > 192.168.2.30 (192.168.2.30) > User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) > Session Initiation Protocol > Request-Line: NOTIFY sip:1001@192.168.2.30;transport=udp SIP/2.0 > Message Header > Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKQ656yDjS3mavS > Transport: UDP > Sent-by Address: 192.168.2.41 > RPort: rport > Branch: z9hG4bKQ656yDjS3mavS > Max-Forwards: 70 > From: <sip:1001@192.168.2.41>;tag=eQH9S8pjtvp6N > To: <sip:1001@192.168.2.41 > >;tag=286229214fa041cb4fa80fb2_F1001192.168.2.30 > Call-ID: 1_7c8e554c7b5cb4fa80abf_S@192.168.2.30 > CSeq: 27613481 NOTIFY > Sequence Number: 27613481 > Method: NOTIFY > * Contact: <sip:1001@192.168.2.41:5060>* > User-Agent: FreeSWITCH-mod_sofia/1.0.6-hacked-20120317T221523Z > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, > REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE > Supported: timer, precondition, path, replaces > Event: message-summary > Allow-Events: talk, presence, dialog, line-seize, call-info, sla, > include-session-description, presence.winfo, message-summary, refer > Subscription-State: active;expires=21 > Content-Type: application/simple-message-summary > Content-Length: 91 > Message Body > Messages-Waiting: yes\r\n > Message-Account: sip:1001@192.168.2.41\r\n > Voice-Message: 1/0 (0/0)\r\n > \r\n > > BROKEN VERSION LATEST GIT > No. Time Source Destination Protocol > Length Info > 6824 18:33:12 192.168.2.41 192.168.2.30 SIP > 1034 Request: NOTIFY sip:1001@192.168.2.30;transport=udp > > Frame 6824: 1034 bytes on wire (8272 bits), 1034 bytes captured (8272 bits) > Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst: > Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f) > Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst: > 192.168.2.30 (192.168.2.30) > User Datagram Protocol, Src Port: sip (5060), Dst Port: iad2 (1031) > Session Initiation Protocol > Request-Line: NOTIFY sip:1001@192.168.2.30;transport=udp SIP/2.0 > Message Header > Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKyyreB17m4eS1c > Transport: UDP > Sent-by Address: 192.168.2.41 > RPort: rport > Branch: z9hG4bKyyreB17m4eS1c > Max-Forwards: 70 > From: <sip:1001@192.168.2.41>;tag=Oa5sgbB1o7sl > SIP from address: sip:1001@192.168.2.41 > SIP tag: Oa5sgbB1o7sl > To: <sip:1001@192.168.2.41 > >;tag=2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30 > SIP to address: sip:1001@192.168.2.41 > SIP to address User Part: 1001 > SIP to address Host Part: 192.168.2.41 > SIP tag: 2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30 > Call-ID: 7_2c27465e595004fa2f77c_S@192.168.2.30 > CSeq: 231978492 NOTIFY > Sequence Number: 231978492 > Method: NOTIFY > * Contact: <sip:1001@192.168.2.41:5060;transport=udp> > Contact-URI: sip:1001@192.168.2.41:5060;transport=udp > Contactt-URI User Part: 1001 > Contact-URI Host Part: 192.168.2.41 > Contact-URI Host Port: 5060 > Contact parameter: transport=udp>* > User-Agent: FreeSWITCH-mod_sofia/1.1.beta1-git-de019ab 2012-05-03 > 15-23-57 +0200 > Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, > REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE > Supported: timer, precondition, path, replaces > Event: message-summary > Allow-Events: talk, hold, presence, dialog, line-seize, call-info, > sla, include-session-description, presence.winfo, message-summary, refer > Subscription-State: active;expires=60 > Content-Type: application/simple-message-summary > Content-Length: 91 > Message Body > Messages-Waiting: yes\r\n > Message-Account: sip:1001@192.168.2.41\r\n > Voice-Message: 2/0 (0/0)\r\n > \r\n > > thanks as ever ! > Bernie > > > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > FreeSWITCH-powered IP PBX: The CudaTel Communication Server > http://www.cudatel.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://wiki.freeswitch.org > http://www.cluecon.com > > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > >
6 May
6 May
8:18 a.m.
thanks for the suggestion, but contact-params is not set at all On Sat, May 5, 2012 at 10:19 PM, DJB International <djbinter@gmail.com>wrote: > What do you have it set for contact-params in your sip profile? > > -djbinter > > On Sat, May 5, 2012 at 9:15 AM, Bernard Murphy < > bernard.david.murphy@gmail.com> wrote: > >> On anything newer than 1.06 of freeswitch the SIP NOTIFY sent to an Avaya >> 9630 phone does not get accepted and trigger the MWI light. Works >> absolutely fine on 1.0.6. >> >> The only difference in the messages i can see is in the contact >> parameter, possibly to do with the angle bracket. Can anyone advise if the >> difference shown in the two messages below is acceptable SIP or if >> something is broken in freeswitch. Also, I'm happy to plough through code >> and try to fix if you can point me in the right direction as to which src >> file constructs the SIP Notify message ? >> >> WORKING VERSION 1.0.6 >> No. Time Source Destination Protocol >> Length Info >> 1169 19:32:47 192.168.2.41 192.168.2.30 SIP >> 996 Request: NOTIFY sip:1001@192.168.2.30;transport=udp >> >> Frame 1169: 996 bytes on wire (7968 bits), 996 bytes captured (7968 bits) >> Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst: >> Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f) >> Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst: >> 192.168.2.30 (192.168.2.30) >> User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060) >> Session Initiation Protocol >> Request-Line: NOTIFY sip:1001@192.168.2.30;transport=udp SIP/2.0 >> Message Header >> Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKQ656yDjS3mavS >> Transport: UDP >> Sent-by Address: 192.168.2.41 >> RPort: rport >> Branch: z9hG4bKQ656yDjS3mavS >> Max-Forwards: 70 >> From: <sip:1001@192.168.2.41>;tag=eQH9S8pjtvp6N >> To: <sip:1001@192.168.2.41 >> >;tag=286229214fa041cb4fa80fb2_F1001192.168.2.30 >> Call-ID: 1_7c8e554c7b5cb4fa80abf_S@192.168.2.30 >> CSeq: 27613481 NOTIFY >> Sequence Number: 27613481 >> Method: NOTIFY >> * Contact: <sip:1001@192.168.2.41:5060>* >> User-Agent: FreeSWITCH-mod_sofia/1.0.6-hacked-20120317T221523Z >> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, >> REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE >> Supported: timer, precondition, path, replaces >> Event: message-summary >> Allow-Events: talk, presence, dialog, line-seize, call-info, sla, >> include-session-description, presence.winfo, message-summary, refer >> Subscription-State: active;expires=21 >> Content-Type: application/simple-message-summary >> Content-Length: 91 >> Message Body >> Messages-Waiting: yes\r\n >> Message-Account: sip:1001@192.168.2.41\r\n >> Voice-Message: 1/0 (0/0)\r\n >> \r\n >> >> BROKEN VERSION LATEST GIT >> No. Time Source Destination Protocol >> Length Info >> 6824 18:33:12 192.168.2.41 192.168.2.30 SIP >> 1034 Request: NOTIFY sip:1001@192.168.2.30;transport=udp >> >> Frame 6824: 1034 bytes on wire (8272 bits), 1034 bytes captured (8272 >> bits) >> Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst: >> Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f) >> Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst: >> 192.168.2.30 (192.168.2.30) >> User Datagram Protocol, Src Port: sip (5060), Dst Port: iad2 (1031) >> Session Initiation Protocol >> Request-Line: NOTIFY sip:1001@192.168.2.30;transport=udp SIP/2.0 >> Message Header >> Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKyyreB17m4eS1c >> Transport: UDP >> Sent-by Address: 192.168.2.41 >> RPort: rport >> Branch: z9hG4bKyyreB17m4eS1c >> Max-Forwards: 70 >> From: <sip:1001@192.168.2.41>;tag=Oa5sgbB1o7sl >> SIP from address: sip:1001@192.168.2.41 >> SIP tag: Oa5sgbB1o7sl >> To: <sip:1001@192.168.2.41 >> >;tag=2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30 >> SIP to address: sip:1001@192.168.2.41 >> SIP to address User Part: 1001 >> SIP to address Host Part: 192.168.2.41 >> SIP tag: 2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30 >> Call-ID: 7_2c27465e595004fa2f77c_S@192.168.2.30 >> CSeq: 231978492 NOTIFY >> Sequence Number: 231978492 >> Method: NOTIFY >> * Contact: <sip:1001@192.168.2.41:5060;transport=udp> >> Contact-URI: sip:1001@192.168.2.41:5060;transport=udp >> Contactt-URI User Part: 1001 >> Contact-URI Host Part: 192.168.2.41 >> Contact-URI Host Port: 5060 >> Contact parameter: transport=udp>* >> User-Agent: FreeSWITCH-mod_sofia/1.1.beta1-git-de019ab 2012-05-03 >> 15-23-57 +0200 >> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, >> REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE >> Supported: timer, precondition, path, replaces >> Event: message-summary >> Allow-Events: talk, hold, presence, dialog, line-seize, >> call-info, sla, include-session-description, presence.winfo, >> message-summary, refer >> Subscription-State: active;expires=60 >> Content-Type: application/simple-message-summary >> Content-Length: 91 >> Message Body >> Messages-Waiting: yes\r\n >> Message-Account: sip:1001@192.168.2.41\r\n >> Voice-Message: 2/0 (0/0)\r\n >> \r\n >> >> thanks as ever ! >> Bernie >> >> >> >> _________________________________________________________________________ >> Professional FreeSWITCH Consulting Services: >> consulting@freeswitch.org >> http://www.freeswitchsolutions.com >> >> FreeSWITCH-powered IP PBX: The CudaTel Communication Server >> http://www.cudatel.com >> >> Official FreeSWITCH Sites >> http://www.freeswitch.org >> http://wiki.freeswitch.org >> http://www.cluecon.com >> >> FreeSWITCH-users mailing list >> FreeSWITCH-users@lists.freeswitch.org >> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users >> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users >> http://www.freeswitch.org >> >> > > _________________________________________________________________________ > Professional FreeSWITCH Consulting Services: > consulting@freeswitch.org > http://www.freeswitchsolutions.com > > FreeSWITCH-powered IP PBX: The CudaTel Communication Server > http://www.cudatel.com > > Official FreeSWITCH Sites > http://www.freeswitch.org > http://wiki.freeswitch.org > http://www.cluecon.com > > FreeSWITCH-users mailing list > FreeSWITCH-users@lists.freeswitch.org > http://lists.freeswitch.org/mailman/listinfo/freeswitch-users > UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users > http://www.freeswitch.org > >
8 May
8 May
1:15 a.m.
On Sat, May 5, 2012 at 10:15 AM, Bernard Murphy <bernard.david.murphy@gmail.com> wrote:
On anything newer than 1.06 of freeswitch the SIP NOTIFY sent to an Avaya 9630 phone does not get accepted and trigger the MWI light. Works absolutely fine on 1.0.6.
Time to file a bug in Jira? Gabe
5293
Age (days ago)
5296
Last active (days ago)
3 comments
3 participants
participants (3)
-
Bernard Murphy
-
DJB International
-
Gabriel Gunderson