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.<br><br>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 ?<br>
<br>WORKING VERSION 1.0.6<br>No. Time Source Destination Protocol Length Info<br> 1169 19:32:47 192.168.2.41 192.168.2.30 SIP 996 Request: NOTIFY <a href="mailto:sip%3A1001@192.168.2.30">sip:1001@192.168.2.30</a>;transport=udp<br>
<br>Frame 1169: 996 bytes on wire (7968 bits), 996 bytes captured (7968 bits)<br>Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst: Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f)<br>Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst: 192.168.2.30 (192.168.2.30)<br>
User Datagram Protocol, Src Port: sip (5060), Dst Port: sip (5060)<br>Session Initiation Protocol<br> Request-Line: NOTIFY <a href="mailto:sip%3A1001@192.168.2.30">sip:1001@192.168.2.30</a>;transport=udp SIP/2.0<br> Message Header<br>
Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKQ656yDjS3mavS<br> Transport: UDP<br> Sent-by Address: 192.168.2.41<br> RPort: rport<br> Branch: z9hG4bKQ656yDjS3mavS<br>
Max-Forwards: 70<br> From: <<a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a>>;tag=eQH9S8pjtvp6N<br> To: <<a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a>>;tag=286229214fa041cb4fa80fb2_F1001192.168.2.30<br>
Call-ID: <a href="mailto:1_7c8e554c7b5cb4fa80abf_S@192.168.2.30">1_7c8e554c7b5cb4fa80abf_S@192.168.2.30</a><br> CSeq: 27613481 NOTIFY<br> Sequence Number: 27613481<br> Method: NOTIFY<br>
<b> Contact: <<a href="http://sip:1001@192.168.2.41:5060">sip:1001@192.168.2.41:5060</a>></b><br> User-Agent: FreeSWITCH-mod_sofia/1.0.6-hacked-20120317T221523Z<br> Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br>
Supported: timer, precondition, path, replaces<br> Event: message-summary<br> Allow-Events: talk, presence, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer<br>
Subscription-State: active;expires=21<br> Content-Type: application/simple-message-summary<br> Content-Length: 91<br> Message Body<br> Messages-Waiting: yes\r\n<br> Message-Account: <a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a>\r\n<br>
Voice-Message: 1/0 (0/0)\r\n<br> \r\n<br><br>BROKEN VERSION LATEST GIT<br>No. Time Source Destination Protocol Length Info<br> 6824 18:33:12 192.168.2.41 192.168.2.30 SIP 1034 Request: NOTIFY <a href="mailto:sip%3A1001@192.168.2.30">sip:1001@192.168.2.30</a>;transport=udp<br>
<br>Frame 6824: 1034 bytes on wire (8272 bits), 1034 bytes captured (8272 bits)<br>Ethernet II, Src: Vmware_1b:7d:13 (00:0c:29:1b:7d:13), Dst: Tenovis_b6:ec:4f (00:07:3b:b6:ec:4f)<br>Internet Protocol Version 4, Src: 192.168.2.41 (192.168.2.41), Dst: 192.168.2.30 (192.168.2.30)<br>
User Datagram Protocol, Src Port: sip (5060), Dst Port: iad2 (1031)<br>Session Initiation Protocol<br> Request-Line: NOTIFY <a href="mailto:sip%3A1001@192.168.2.30">sip:1001@192.168.2.30</a>;transport=udp SIP/2.0<br> Message Header<br>
Via: SIP/2.0/UDP 192.168.2.41;rport;branch=z9hG4bKyyreB17m4eS1c<br> Transport: UDP<br> Sent-by Address: 192.168.2.41<br> RPort: rport<br> Branch: z9hG4bKyyreB17m4eS1c<br>
Max-Forwards: 70<br> From: <<a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a>>;tag=Oa5sgbB1o7sl<br> SIP from address: <a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a><br>
SIP tag: Oa5sgbB1o7sl<br> To: <<a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a>>;tag=2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30<br> SIP to address: <a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a><br>
SIP to address User Part: 1001<br> SIP to address Host Part: 192.168.2.41<br> SIP tag: 2b269bdd4fa034ed4fa2ffe4_F1001192.168.2.30<br> Call-ID: <a href="mailto:7_2c27465e595004fa2f77c_S@192.168.2.30">7_2c27465e595004fa2f77c_S@192.168.2.30</a><br>
CSeq: 231978492 NOTIFY<br> Sequence Number: 231978492<br> Method: NOTIFY<br> <b> Contact: <sip:1001@192.168.2.41:5060;transport=udp><br> Contact-URI: sip:1001@192.168.2.41:5060;transport=udp<br>
Contactt-URI User Part: 1001<br> Contact-URI Host Part: 192.168.2.41<br> Contact-URI Host Port: 5060<br> Contact parameter: transport=udp></b><br> User-Agent: FreeSWITCH-mod_sofia/1.1.beta1-git-de019ab 2012-05-03 15-23-57 +0200<br>
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, UPDATE, INFO, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE<br> Supported: timer, precondition, path, replaces<br> Event: message-summary<br> Allow-Events: talk, hold, presence, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer<br>
Subscription-State: active;expires=60<br> Content-Type: application/simple-message-summary<br> Content-Length: 91<br> Message Body<br> Messages-Waiting: yes\r\n<br> Message-Account: <a href="mailto:sip%3A1001@192.168.2.41">sip:1001@192.168.2.41</a>\r\n<br>
Voice-Message: 2/0 (0/0)\r\n<br> \r\n<br><br>thanks as ever !<br>Bernie<br><br><br>