jlumby Posted May 20, 2008 Report Share Posted May 20, 2008 I have discovered through Cisco's documentation that the 79x1 phones first tries to set the date and time off of the SIP registration responce, and then they fine tune it off of the NTP server that is listed in their config file. I am having an issue that since the date, and time is not sent in the SIP messaging to the phone, that the clock never gets close enough to use the NTP server. Is there a way to make PBXnSIP send the date, or does anyone know of a workaround? Below is a copy of how a Cisco sends the date from their callmanager. No. Time Source Destination Protocol Info 229 70.598879 192.168.5.199 192.168.5.138 SIP Status: 200 OK (1 bindings) Frame 229 (650 bytes on wire, 650 bytes captured) Ethernet II, Src: CompaqHp_af:1a:24 (00:0b:cd:af:1a:24), Dst: Cisco_84:61:80 (00:1b:d5:84:61:80) Internet Protocol, Src: 192.168.5.199 (192.168.5.199), Dst: 192.168.5.138 (192.168.5.138) Transmission Control Protocol, Src Port: sip (5060), Dst Port: 50294 (50294), Seq: 639, Ack: 1716, Len: 596 Source port: sip (5060) Destination port: 50294 (50294) Sequence number: 639 (relative sequence number) [Next sequence number: 1235 (relative sequence number)] Acknowledgement number: 1716 (relative ack number) Header length: 20 bytes Flags: 0x18 (PSH, ACK) 0... .... = Congestion Window Reduced (CWR): Not set .0.. .... = ECN-Echo: Not set ..0. .... = Urgent: Not set ...1 .... = Acknowledgment: Set .... 1... = Push: Set .... .0.. = Reset: Not set .... ..0. = Syn: Not set .... ...0 = Fin: Not set Window size: 9684 Checksum: 0x4de6 [correct] [sEQ/ACK analysis] [This is an ACK to the segment in frame: 228] [The RTT to ACK the segment was: 0.495541000 seconds] Session Initiation Protocol Status-Line: SIP/2.0 200 OK Status-Code: 200 [Resent Packet: False] Message Header Via: SIP/2.0/TCP 192.168.5.138:50294;branch=z9hG4bK47aff438 From: <sip:1009@192.168.5.199>;tag=001bd584618000022a3003a8-470cfe78 SIP from address: sip:1009@192.168.5.199 SIP tag: 001bd584618000022a3003a8-470cfe78 To: <sip:1009@192.168.5.199>;tag=436104038 SIP to address: sip:1009@192.168.5.199 SIP tag: 436104038 Date: Tue, 20 May 2008 22:04:19 GMT Call-ID: 001bd584-61800003-92fe3868-3a9464b8@192.168.5.138 CSeq: 101 REGISTER Sequence Number: 101 Method: REGISTER Expires: 120 Contact: <sip:00857d4c-4c71-4a69-8590-2714e50f8c3c@192.168.5.138:50294;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-001bd5846180>";+u.sip!model.ccm.cisco.com="30018";x-cisco-newreg Contact Binding: <sip:00857d4c-4c71-4a69-8590-2714e50f8c3c@192.168.5.138:50294;transport=tcp>;+sip.instance="<urn:uuid:00000000-0000-0000-0000-001bd5846180>";+u.sip!model.ccm.cisco.com="30018";x-cisco-newreg Supported: X-cisco-srtp-fallback,X-cisco-sis-2.0.0 Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 20, 2008 Report Share Posted May 20, 2008 I have discovered through Cisco's documentation that the 79x1 phones first tries to set the date and time off of the SIP registration responce, and then they fine tune it off of the NTP server that is listed in their config file. I am having an issue that since the date, and time is not sent in the SIP messaging to the phone, that the clock never gets close enough to use the NTP server. Is there a way to make PBXnSIP send the date, or does anyone know of a workaround? Below is a copy of how a Cisco sends the date from their callmanager. Whow. Actually it is no big problem to put that in. Is GMT always fine or does the phone expect "local" time (wherever the phone is)? Quote Link to comment Share on other sites More sharing options...
jlumby Posted May 21, 2008 Author Report Share Posted May 21, 2008 The phone always expects GMT, and it adjusts it based upon the timezone specified in the xml config file that the phone downloads from the pbx at bootup. Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted May 21, 2008 Report Share Posted May 21, 2008 The phone always expects GMT, and it adjusts it based upon the timezone specified in the xml config file that the phone downloads from the pbx at bootup. Okay, we put that into the head version, will be in the upcoming releases of 3.x. Quote Link to comment Share on other sites More sharing options...
Nugget Posted November 27, 2008 Report Share Posted November 27, 2008 Via: SIP/2.0/TCP 192.168.5.138:50294;branch=z9hG4bK47aff438 What's the magic .cnf.xml that can get a 79x1 talking SIP/TCP? That's what I'm dying to know! Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted November 27, 2008 Report Share Posted November 27, 2008 What's the magic .cnf.xml that can get a 79x1 talking SIP/TCP? That's what I'm dying to know! I also don't know. There are many things I don't know with the .cnf.xml files..... Quote Link to comment Share on other sites More sharing options...
jlumby Posted November 28, 2008 Author Report Share Posted November 28, 2008 The trick is to set the proxy on each line to USECALLMANAGER and then define the ip or FQND of the pbxnsip server in the callmanager section of the xml config file Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.