mabbott

Is this a feature in the current builds, or is this still just a possibility?

Windows 2003 Server and OSX 10.5.6.

If you enter invalid web login credentials multiple times, the pbx service crashes. I have had this happen from anywhere between 3 and 12 failed login attempts with both Windows and OSX using version 3.1.2.3120.

The Wiki has instructions for setting up the Cbeyond service with pbxnsip. Is pbxnsip officially complaint/partnered with Cbeyond for using their service with the pbx?

I have a black system that is rebooting several times a day. It is running PBXnSIP version 3.0.1.3023 and sipfxo-release shows sipfxo 0.86, MSP m828_v2_03_1, VAPI Library Release 2.4.2, API Version 4.0. The OS does seem to be rebooting. Like other posters, the system is on a UPS and has a strong password. Could I be having the same problem? Thanks.

I am trying to provision some additional settings using this method, but when the phone requests the xml file, it gets redirected to the login page. Is there a way to get around this redirection? I am using 3.0.0.2998

I am trying to setup multicast paging using Snom phones as the destination. I have Multicast enabled on the phones with the multicast IP/port matching what I have entered in the paging account. When I call the extension the phone connects but the page doesn't go through. Doing a packet capture shows the audio stream going from the phone to the PBX, but I do not see any multicast traffic leaving the pbx. Are there any other places I need to enable multicast support to enable the paging? I am using 3.0.0.2998 on the cs410 and 7.1.35 on the phones.

That doesn't seem to be what is happening. It is getting the message to turn on button 13, but the symbol isn't appearing. Button 13 on the pbx is a DND and I changed the function key for DND to a button type instead of key event and put in 13. Anything else I need to set to make it appear?

I saw that with 7.1.33 the DND function key can be set up to use the buttons package with PBXNSIP. If using it in this way does it show the DND icon on the display to show the status from the pbx instead of showing the light next to a standard function key?

I have been experiencing an intermittent problem with DND not turning off using snom's with 7.1.33. It seems like the phone is dialing the *79 to deactivate it because I see the call appearance light up when I press that key and the DND icon goes away on the phone goes away, but the pbx doesn't turn it off. I can't be 100% sure that the pbx is getting the *79 invite because by the time it is noticed that DND is still enabled, there have been several calls and it has been pushed out of the logs. Has anyone else been experiencing this?

Yes, I think the delay was about 1 sec on this call, but it does seem to vary a little bit. It does seem to only happen when calling their hunt group. I tried an extension directly and the auto attendant and both seemed to have no delay connecting the audio stream. There is 4 extensions in stage 1 of the hunt group(none in the other 2 stages), is that to many?

Here is the tcpdump from the pbx.

There is no delay in the audio connecting when dialed directly from another extension. I will not be able to get a hub there to plug with the pbx. Would it be possible to do the capture from the appliance itself?

On inbound calls there seems to be a delay of between 2-5 seconds from when I answer the call to when the RTP stream is established to the ITSP. Below is the call log. The delay on this call was prob 2sec. The phone is a snom 360 7.1.30 and the ITSP is NexVortex. Thanks, Martin [9] 2008/07/09 12:06:40: SIP Rx udp:66.23.129.253:5060: INVITE sip:14135844190@75.150.102.90 SIP/2.0 Record-Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK4eee.3de6c972.0 Via: SIP/2.0/UDP 69.30.45.229:5061;branch=z9hG4bK1fd93fef3e646235741b1d4c66ac6f10;rport=5061 Max-Forwards: 16 From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253> Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 INVITE Contact: Anonymous <sip:69.30.45.229:5061> Expires: 300 User-Agent: Sippy cisco-GUID: 2366249941-2517129136-1320601400-1573133248 h323-conf-id: 2366249941-2517129136-1320601400-1573133248 Content-Length: 173 Content-Type: application/sdp v=0 o=Sippy 152004300 0 IN IP4 69.30.45.229 s=sip call t=0 0 m=audio 45578 RTP/AVP 0 18 101 c=IN IP4 66.234.135.60 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 [5] 2008/07/09 12:06:40: Identify trunk (IP address/port and domain match) 2 [9] 2008/07/09 12:06:40: Resolve 38548: aaaa udp 66.23.129.253 5060 [9] 2008/07/09 12:06:40: Resolve 38548: a udp 66.23.129.253 5060 [9] 2008/07/09 12:06:40: Resolve 38548: udp 66.23.129.253 5060 [9] 2008/07/09 12:06:40: SIP Tx udp:66.23.129.253:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK4eee.3de6c972.0 Via: SIP/2.0/UDP 69.30.45.229:5061;branch=z9hG4bK1fd93fef3e646235741b1d4c66ac6f10;rport=5061 Record-Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 INVITE Content-Length: 0 [5] 2008/07/09 12:06:40: Trunk nexVortex sends call to 100 [9] 2008/07/09 12:06:40: Resolve 38549: aaaa udp 66.23.129.253 5060 [9] 2008/07/09 12:06:40: Resolve 38549: a udp 66.23.129.253 5060 [9] 2008/07/09 12:06:40: Resolve 38549: udp 66.23.129.253 5060 [9] 2008/07/09 12:06:40: SIP Tx udp:66.23.129.253:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK4eee.3de6c972.0 Via: SIP/2.0/UDP 69.30.45.229:5061;branch=z9hG4bK1fd93fef3e646235741b1d4c66ac6f10;rport=5061 Record-Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 INVITE Contact: <sip:chambersadvisory@75.150.102.90:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 202 v=0 o=- 573161756 573161756 IN IP4 75.150.102.90 s=- c=IN IP4 75.150.102.90 t=0 0 m=audio 54438 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38550: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:40: Resolve 38550: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: Resolve 38550: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: SIP Tx tls:192.168.1.71:2058: INVITE sip:241@192.168.1.71:2051;transport=tls;line=9autualr SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-080edf589588351f444d38c81071d3e2;rport From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253> Call-ID: bcc8c22d@pbx CSeq: 23705 INVITE Max-Forwards: 70 Contact: <sip:241@192.168.1.2:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 382 v=0 o=- 1694082291 1694082291 IN IP4 192.168.1.2 s=- c=IN IP4 192.168.1.2 t=0 0 m=audio 53474 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:Lnp7n3Tjgd4vb2HbGdBp3gRt/hagQLsk2rQ0vVvD a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38551: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:40: Resolve 38551: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: Resolve 38551: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38552: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:40: Resolve 38552: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:40: Resolve 38552: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38553: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:40: Resolve 38553: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:40: Resolve 38553: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38554: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:40: Resolve 38554: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:40: Resolve 38554: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38555: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:40: Resolve 38555: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:40: Resolve 38555: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38556: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:40: Resolve 38556: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:40: Resolve 38556: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38557: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:40: Resolve 38557: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:40: Resolve 38557: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:40: SIP Tx tls:192.168.1.66:2067: INVITE sip:242@192.168.1.66:2054;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-022086b504c16f9620a81304a4211f71;rport From: <sip:6038704447@69.30.45.229>;tag=1937225949 To: <sip:14135844190@66.23.129.253> Call-ID: d5cd8888@pbx CSeq: 13656 INVITE Max-Forwards: 70 Contact: <sip:242@192.168.1.2:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 382 v=0 o=- 1771756573 1771756573 IN IP4 192.168.1.2 s=- c=IN IP4 192.168.1.2 t=0 0 m=audio 58098 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:CLk5MAoX2mu8c9s9m5pVd4O6O1PGq7kDA+Ga9to1 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38558: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:40: Resolve 38558: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: Resolve 38558: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38559: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:40: Resolve 38559: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:40: Resolve 38559: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38560: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:40: Resolve 38560: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:40: Resolve 38560: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38561: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:40: Resolve 38561: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:40: Resolve 38561: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38562: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:40: Resolve 38562: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:40: Resolve 38562: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38563: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:40: Resolve 38563: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:40: Resolve 38563: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38564: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:40: Resolve 38564: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:40: Resolve 38564: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:40: SIP Tx tls:192.168.1.72:2057: INVITE sip:243@192.168.1.72:2051;transport=tls;line=8fwoplsv SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-4ad229094fc7922fb626361ec84db321;rport From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253> Call-ID: 966061d5@pbx CSeq: 25202 INVITE Max-Forwards: 70 Contact: <sip:243@192.168.1.2:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 382 v=0 o=- 1794262104 1794262104 IN IP4 192.168.1.2 s=- c=IN IP4 192.168.1.2 t=0 0 m=audio 59564 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:aTZcStBSJAZmBvW0GO4ZBFI6Y5GYXWpLz8e5fXfs a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38565: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:40: Resolve 38565: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: Resolve 38565: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:40: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:40: Resolve 38566: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:40: Resolve 38566: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:40: Resolve 38566: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38567: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:41: Resolve 38567: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: Resolve 38567: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38568: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:41: Resolve 38568: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:41: Resolve 38568: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38569: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:41: Resolve 38569: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Resolve 38569: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38570: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:41: Resolve 38570: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:41: Resolve 38570: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38571: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:41: Resolve 38571: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Resolve 38571: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: SIP Tx tls:192.168.1.65:2069: INVITE sip:246@192.168.1.65:2051;transport=tls;line=94aa7mxt SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b3f347eee7ceac44789349d1cdc15af7;rport From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253> Call-ID: 54401329@pbx CSeq: 21360 INVITE Max-Forwards: 70 Contact: <sip:246@192.168.1.2:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 380 v=0 o=- 870078257 870078257 IN IP4 192.168.1.2 s=- c=IN IP4 192.168.1.2 t=0 0 m=audio 63698 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:KtUA8Y59aXpTSZ2EdJEIworzF3mRg1VJ9IQ6x0PE a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38572: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:41: Resolve 38572: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:41: Resolve 38572: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38573: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:41: Resolve 38573: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:41: Resolve 38573: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38574: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:41: Resolve 38574: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: Resolve 38574: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38575: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:41: Resolve 38575: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:41: Resolve 38575: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38576: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:41: Resolve 38576: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Resolve 38576: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38577: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:41: Resolve 38577: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:41: Resolve 38577: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:41: SIP Tr udp:66.23.129.253:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK4eee.3de6c972.0 Via: SIP/2.0/UDP 69.30.45.229:5061;branch=z9hG4bK1fd93fef3e646235741b1d4c66ac6f10;rport=5061 Record-Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 INVITE Contact: <sip:chambersadvisory@75.150.102.90:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 202 v=0 o=- 573161756 573161756 IN IP4 75.150.102.90 s=- c=IN IP4 75.150.102.90 t=0 0 m=audio 54438 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:41: SIP Rx tls:192.168.1.71:2058: SIP/2.0 180 Ringing Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-080edf589588351f444d38c81071d3e2;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253>;tag=nk2f08f3yb Call-ID: bcc8c22d@pbx CSeq: 23705 INVITE Contact: <sip:241@192.168.1.71:2051;transport=tls;line=9autualr>;flow-id=1 Require: 100rel RSeq: 1 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Content-Length: 0 [9] 2008/07/09 12:06:41: Resolve 38578: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:41: Resolve 38578: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:41: Resolve 38578: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:41: SIP Tx tls:192.168.1.71:2058: PRACK sip:241@192.168.1.71:2051;transport=tls;line=9autualr SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b990e0b9da04ac4182315310ce651c4d;rport From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253>;tag=nk2f08f3yb Call-ID: bcc8c22d@pbx CSeq: 23706 PRACK Max-Forwards: 70 Contact: <sip:241@192.168.1.2:5061;transport=tls> RAck: 1 23705 INVITE Content-Length: 0 [9] 2008/07/09 12:06:41: SIP Rx tls:192.168.1.72:2057: SIP/2.0 180 Ringing Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-4ad229094fc7922fb626361ec84db321;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253>;tag=g4j8bu3i4q Call-ID: 966061d5@pbx CSeq: 25202 INVITE Contact: <sip:243@192.168.1.72:2051;transport=tls;line=8fwoplsv>;flow-id=1 Require: 100rel RSeq: 1 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Content-Length: 0 [9] 2008/07/09 12:06:41: Resolve 38579: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:41: Resolve 38579: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: Resolve 38579: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: SIP Tx tls:192.168.1.72:2057: PRACK sip:243@192.168.1.72:2051;transport=tls;line=8fwoplsv SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-9d9fe0b4c2a482e418311eda32f96f4b;rport From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253>;tag=g4j8bu3i4q Call-ID: 966061d5@pbx CSeq: 25203 PRACK Max-Forwards: 70 Contact: <sip:243@192.168.1.2:5061;transport=tls> RAck: 1 25202 INVITE Content-Length: 0 [9] 2008/07/09 12:06:41: SIP Rx tls:192.168.1.65:2069: SIP/2.0 180 Ringing Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b3f347eee7ceac44789349d1cdc15af7;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253>;tag=pr825c9fzk Call-ID: 54401329@pbx CSeq: 21360 INVITE Contact: <sip:246@192.168.1.65:2051;transport=tls;line=94aa7mxt>;flow-id=1 Require: 100rel RSeq: 1 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Content-Length: 0 [9] 2008/07/09 12:06:41: Resolve 38580: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:41: Resolve 38580: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Resolve 38580: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: SIP Tx tls:192.168.1.65:2069: PRACK sip:246@192.168.1.65:2051;transport=tls;line=94aa7mxt SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-5ef56ab81135039f73b0a307044326e5;rport From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253>;tag=pr825c9fzk Call-ID: 54401329@pbx CSeq: 21361 PRACK Max-Forwards: 70 Contact: <sip:246@192.168.1.2:5061;transport=tls> RAck: 1 21360 INVITE Content-Length: 0 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38581: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:41: Resolve 38581: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:41: Resolve 38581: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38582: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:41: Resolve 38582: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:41: Resolve 38582: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38583: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:41: Resolve 38583: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: Resolve 38583: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38584: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:41: Resolve 38584: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:41: Resolve 38584: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38585: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:41: Resolve 38585: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Resolve 38585: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:41: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:41: Resolve 38586: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:41: Resolve 38586: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:41: Resolve 38586: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:41: SIP Rx tls:192.168.1.72:2057: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-9d9fe0b4c2a482e418311eda32f96f4b;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253>;tag=g4j8bu3i4q Call-ID: 966061d5@pbx CSeq: 25203 PRACK Contact: <sip:243@192.168.1.72:2051;transport=tls;line=8fwoplsv>;flow-id=1 Content-Length: 0 [7] 2008/07/09 12:06:41: Call 966061d5@pbx#1608372825: Clear last request [9] 2008/07/09 12:06:41: SIP Rx tls:192.168.1.66:2067: SIP/2.0 180 Ringing Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-022086b504c16f9620a81304a4211f71;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1937225949 To: <sip:14135844190@66.23.129.253>;tag=vshqvory73 Call-ID: d5cd8888@pbx CSeq: 13656 INVITE Contact: <sip:242@192.168.1.66:2054;transport=tls>;flow-id=1 Require: 100rel RSeq: 1 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Content-Length: 0 [9] 2008/07/09 12:06:41: Resolve 38587: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:41: Resolve 38587: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:41: Resolve 38587: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:41: SIP Tx tls:192.168.1.66:2067: PRACK sip:242@192.168.1.66:2054;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-8582ce0e3db2274951a67d0932c26284;rport From: <sip:6038704447@69.30.45.229>;tag=1937225949 To: <sip:14135844190@66.23.129.253>;tag=vshqvory73 Call-ID: d5cd8888@pbx CSeq: 13657 PRACK Max-Forwards: 70 Contact: <sip:242@192.168.1.2:5061;transport=tls> RAck: 1 13656 INVITE Content-Length: 0 [9] 2008/07/09 12:06:41: SIP Rx tls:192.168.1.65:2069: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-5ef56ab81135039f73b0a307044326e5;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253>;tag=pr825c9fzk Call-ID: 54401329@pbx CSeq: 21361 PRACK Contact: <sip:246@192.168.1.65:2051;transport=tls;line=94aa7mxt>;flow-id=1 Content-Length: 0 [7] 2008/07/09 12:06:41: Call 54401329@pbx#1791939203: Clear last request [9] 2008/07/09 12:06:41: SIP Rx tls:192.168.1.71:2058: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b990e0b9da04ac4182315310ce651c4d;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253>;tag=nk2f08f3yb Call-ID: bcc8c22d@pbx CSeq: 23706 PRACK Contact: <sip:241@192.168.1.71:2051;transport=tls;line=9autualr>;flow-id=1 Content-Length: 0 [7] 2008/07/09 12:06:41: Call bcc8c22d@pbx#941696822: Clear last request [9] 2008/07/09 12:06:42: SIP Tr udp:66.23.129.253:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK4eee.3de6c972.0 Via: SIP/2.0/UDP 69.30.45.229:5061;branch=z9hG4bK1fd93fef3e646235741b1d4c66ac6f10;rport=5061 Record-Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 INVITE Contact: <sip:chambersadvisory@75.150.102.90:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 202 v=0 o=- 573161756 573161756 IN IP4 75.150.102.90 s=- c=IN IP4 75.150.102.90 t=0 0 m=audio 54438 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:42: SIP Rx tls:192.168.1.66:2067: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-8582ce0e3db2274951a67d0932c26284;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1937225949 To: <sip:14135844190@66.23.129.253>;tag=vshqvory73 Call-ID: d5cd8888@pbx CSeq: 13657 PRACK Contact: <sip:242@192.168.1.66:2054;transport=tls>;flow-id=1 Content-Length: 0 [7] 2008/07/09 12:06:42: Call d5cd8888@pbx#1937225949: Clear last request [8] 2008/07/09 12:06:43: Packet authenticated by transport layer [9] 2008/07/09 12:06:43: Resolve 38588: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:44: SIP Tr udp:66.23.129.253:5060: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK4eee.3de6c972.0 Via: SIP/2.0/UDP 69.30.45.229:5061;branch=z9hG4bK1fd93fef3e646235741b1d4c66ac6f10;rport=5061 Record-Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 INVITE Contact: <sip:chambersadvisory@75.150.102.90:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 202 v=0 o=- 573161756 573161756 IN IP4 75.150.102.90 s=- c=IN IP4 75.150.102.90 t=0 0 m=audio 54438 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:45: SIP Rx tls:192.168.1.66:2067: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-022086b504c16f9620a81304a4211f71;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1937225949 To: <sip:14135844190@66.23.129.253>;tag=vshqvory73 Call-ID: d5cd8888@pbx CSeq: 13656 INVITE Contact: <sip:242@192.168.1.66:2054;transport=tls>;flow-id=1 User-Agent: snom360/7.1.30 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, callerid Content-Type: application/sdp Content-Length: 411 v=0 o=root 816231848 816231849 IN IP4 192.168.1.66 s=call c=IN IP4 192.168.1.66 t=0 0 m=audio 55788 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:nBqImqmxnyHTb+Xj0eujdFv7WN+jb3dUhbaFacgs a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=encryption:optional a=sendrecv [7] 2008/07/09 12:06:45: Call d5cd8888@pbx#1937225949: Clear last INVITE [9] 2008/07/09 12:06:45: Resolve 38589: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:45: Resolve 38589: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:45: Resolve 38589: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:45: SIP Tx tls:192.168.1.66:2067: ACK sip:242@192.168.1.66:2054;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-00bb06736a506445d0fae5ad86994ad6;rport From: <sip:6038704447@69.30.45.229>;tag=1937225949 To: <sip:14135844190@66.23.129.253>;tag=vshqvory73 Call-ID: d5cd8888@pbx CSeq: 13656 ACK Max-Forwards: 70 Contact: <sip:242@192.168.1.2:5061;transport=tls> Content-Length: 0 [9] 2008/07/09 12:06:45: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:45: Resolve 38590: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:45: Resolve 38590: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:45: Resolve 38590: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:45: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:45: Resolve 38591: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:45: Resolve 38591: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:45: Resolve 38591: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:45: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:45: Resolve 38592: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:45: Resolve 38592: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:45: Resolve 38592: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:45: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:45: Resolve 38593: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:46: Resolve 38593: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Resolve 38593: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38594: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:46: Resolve 38594: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Resolve 38594: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38595: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:46: Resolve 38595: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: Resolve 38595: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: Resolve 38596: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: SIP Tx tls:192.168.1.71:2058: CANCEL sip:241@192.168.1.71:2051;transport=tls;line=9autualr SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-080edf589588351f444d38c81071d3e2;rport From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253> Call-ID: bcc8c22d@pbx CSeq: 23705 CANCEL Max-Forwards: 70 Reason: SIP;cause=200;text="Call completed elsewhere" Content-Length: 0 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38597: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:46: Resolve 38597: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: Resolve 38597: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38598: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:46: Resolve 38598: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:46: Resolve 38598: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38599: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:46: Resolve 38599: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: Resolve 38599: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38600: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:46: Resolve 38600: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Resolve 38600: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38601: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:46: Resolve 38601: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Resolve 38601: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38602: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:46: Resolve 38602: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: Resolve 38602: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: SIP Rx tls:192.168.1.66:2067: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-022086b504c16f9620a81304a4211f71;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1937225949 To: <sip:14135844190@66.23.129.253>;tag=vshqvory73 Call-ID: d5cd8888@pbx CSeq: 13656 INVITE Contact: <sip:242@192.168.1.66:2054;transport=tls>;flow-id=1 User-Agent: snom360/7.1.30 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, callerid Content-Type: application/sdp Content-Length: 411 v=0 o=root 816231848 816231850 IN IP4 192.168.1.66 s=call c=IN IP4 192.168.1.66 t=0 0 m=audio 55788 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:nBqImqmxnyHTb+Xj0eujdFv7WN+jb3dUhbaFacgs a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=encryption:optional a=sendrecv [9] 2008/07/09 12:06:46: Message repetition, packet dropped [8] 2008/07/09 12:06:46: Packet authenticated by transport layer [9] 2008/07/09 12:06:46: SIP Rx tls:192.168.1.71:2058: SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-080edf589588351f444d38c81071d3e2;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253>;tag=nk2f08f3yb Call-ID: bcc8c22d@pbx CSeq: 23705 CANCEL Content-Length: 0 [7] 2008/07/09 12:06:46: Call bcc8c22d@pbx#941696822: Clear last request [9] 2008/07/09 12:06:46: SIP Rx tls:192.168.1.71:2058: SIP/2.0 487 Request Terminated Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-080edf589588351f444d38c81071d3e2;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253>;tag=nk2f08f3yb Call-ID: bcc8c22d@pbx CSeq: 23705 INVITE Contact: <sip:241@192.168.1.71:2051;transport=tls;line=9autualr>;flow-id=1 Content-Length: 0 [7] 2008/07/09 12:06:46: Call bcc8c22d@pbx#941696822: Clear last INVITE [9] 2008/07/09 12:06:46: Resolve 38603: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:46: Resolve 38603: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: Resolve 38603: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: SIP Tx tls:192.168.1.71:2058: ACK sip:241@192.168.1.71:2051;transport=tls;line=9autualr SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-080edf589588351f444d38c81071d3e2;rport From: <sip:6038704447@69.30.45.229>;tag=941696822 To: <sip:14135844190@66.23.129.253>;tag=nk2f08f3yb Call-ID: bcc8c22d@pbx CSeq: 23705 ACK Max-Forwards: 70 Contact: <sip:241@192.168.1.2:5061;transport=tls> Content-Length: 0 [5] 2008/07/09 12:06:46: INVITE Response: Terminate bcc8c22d@pbx [7] 2008/07/09 12:06:46: Other Ports: 6 [7] 2008/07/09 12:06:46: Call Port: 12164841-3424608400-56494@interface-e1000g0#45c8a9d9c8 [7] 2008/07/09 12:06:46: Call Port: 3c2688bd740f-wi7wfa3wkjvo#cf583492ec [7] 2008/07/09 12:06:46: Call Port: 42f6a342@pbx#931656885 [7] 2008/07/09 12:06:46: Call Port: 54401329@pbx#1791939203 [7] 2008/07/09 12:06:46: Call Port: 966061d5@pbx#1608372825 [7] 2008/07/09 12:06:46: Call Port: d5cd8888@pbx#1937225949 [9] 2008/07/09 12:06:46: Resolve 38604: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: SIP Tx tls:192.168.1.72:2057: CANCEL sip:243@192.168.1.72:2051;transport=tls;line=8fwoplsv SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-4ad229094fc7922fb626361ec84db321;rport From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253> Call-ID: 966061d5@pbx CSeq: 25202 CANCEL Max-Forwards: 70 Reason: SIP;cause=200;text="Call completed elsewhere" Content-Length: 0 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38605: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:46: Resolve 38605: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: Resolve 38605: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38606: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:46: Resolve 38606: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:46: Resolve 38606: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38607: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:46: Resolve 38607: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: Resolve 38607: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38608: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:46: Resolve 38608: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Resolve 38608: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38609: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:46: Resolve 38609: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Resolve 38609: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38610: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:46: Resolve 38610: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: Resolve 38610: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: Resolve 38611: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: SIP Tx tls:192.168.1.65:2069: CANCEL sip:246@192.168.1.65:2051;transport=tls;line=94aa7mxt SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b3f347eee7ceac44789349d1cdc15af7;rport From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253> Call-ID: 54401329@pbx CSeq: 21360 CANCEL Max-Forwards: 70 Reason: SIP;cause=200;text="Call completed elsewhere" Content-Length: 0 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38612: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:06:46: Resolve 38612: a tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: Resolve 38612: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38613: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:06:46: Resolve 38613: a tls 192.168.1.66 2067 [9] 2008/07/09 12:06:46: Resolve 38613: tls 192.168.1.66 2067 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38614: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:46: Resolve 38614: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: Resolve 38614: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38615: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:06:46: Resolve 38615: a tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Resolve 38615: tls 192.168.1.10 2056 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38616: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:46: Resolve 38616: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Resolve 38616: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:06:46: Resolve 38617: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:06:46: Resolve 38617: a tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: Resolve 38617: tls 192.168.1.233 2097 [9] 2008/07/09 12:06:46: SIP Rx tls:192.168.1.72:2057: SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-4ad229094fc7922fb626361ec84db321;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253>;tag=g4j8bu3i4q Call-ID: 966061d5@pbx CSeq: 25202 CANCEL Content-Length: 0 [7] 2008/07/09 12:06:46: Call 966061d5@pbx#1608372825: Clear last request [9] 2008/07/09 12:06:46: SIP Rx tls:192.168.1.72:2057: SIP/2.0 487 Request Terminated Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-4ad229094fc7922fb626361ec84db321;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253>;tag=g4j8bu3i4q Call-ID: 966061d5@pbx CSeq: 25202 INVITE Contact: <sip:243@192.168.1.72:2051;transport=tls;line=8fwoplsv>;flow-id=1 Content-Length: 0 [7] 2008/07/09 12:06:46: Call 966061d5@pbx#1608372825: Clear last INVITE [9] 2008/07/09 12:06:46: Resolve 38618: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:06:46: Resolve 38618: a tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: Resolve 38618: tls 192.168.1.72 2057 [9] 2008/07/09 12:06:46: SIP Tx tls:192.168.1.72:2057: ACK sip:243@192.168.1.72:2051;transport=tls;line=8fwoplsv SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-4ad229094fc7922fb626361ec84db321;rport From: <sip:6038704447@69.30.45.229>;tag=1608372825 To: <sip:14135844190@66.23.129.253>;tag=g4j8bu3i4q Call-ID: 966061d5@pbx CSeq: 25202 ACK Max-Forwards: 70 Contact: <sip:243@192.168.1.2:5061;transport=tls> Content-Length: 0 [5] 2008/07/09 12:06:46: INVITE Response: Terminate 966061d5@pbx [7] 2008/07/09 12:06:46: Other Ports: 5 [7] 2008/07/09 12:06:46: Call Port: 12164841-3424608400-56494@interface-e1000g0#45c8a9d9c8 [7] 2008/07/09 12:06:46: Call Port: 3c2688bd740f-wi7wfa3wkjvo#cf583492ec [7] 2008/07/09 12:06:46: Call Port: 42f6a342@pbx#931656885 [7] 2008/07/09 12:06:46: Call Port: 54401329@pbx#1791939203 [7] 2008/07/09 12:06:46: Call Port: d5cd8888@pbx#1937225949 [9] 2008/07/09 12:06:46: SIP Rx tls:192.168.1.65:2069: SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b3f347eee7ceac44789349d1cdc15af7;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253>;tag=pr825c9fzk Call-ID: 54401329@pbx CSeq: 21360 CANCEL Content-Length: 0 [7] 2008/07/09 12:06:46: Call 54401329@pbx#1791939203: Clear last request [9] 2008/07/09 12:06:46: SIP Rx tls:192.168.1.65:2069: SIP/2.0 487 Request Terminated Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b3f347eee7ceac44789349d1cdc15af7;rport=5061 From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253>;tag=pr825c9fzk Call-ID: 54401329@pbx CSeq: 21360 INVITE Contact: <sip:246@192.168.1.65:2051;transport=tls;line=94aa7mxt>;flow-id=1 Content-Length: 0 [7] 2008/07/09 12:06:46: Call 54401329@pbx#1791939203: Clear last INVITE [9] 2008/07/09 12:06:46: Resolve 38619: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:06:46: Resolve 38619: a tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: Resolve 38619: tls 192.168.1.65 2069 [9] 2008/07/09 12:06:46: SIP Tx tls:192.168.1.65:2069: ACK sip:246@192.168.1.65:2051;transport=tls;line=94aa7mxt SIP/2.0 Via: SIP/2.0/TLS 192.168.1.2:5061;branch=z9hG4bK-b3f347eee7ceac44789349d1cdc15af7;rport From: <sip:6038704447@69.30.45.229>;tag=1791939203 To: <sip:14135844190@66.23.129.253>;tag=pr825c9fzk Call-ID: 54401329@pbx CSeq: 21360 ACK Max-Forwards: 70 Contact: <sip:246@192.168.1.2:5061;transport=tls> Content-Length: 0 [5] 2008/07/09 12:06:46: INVITE Response: Terminate 54401329@pbx [7] 2008/07/09 12:06:46: Other Ports: 4 [7] 2008/07/09 12:06:46: Call Port: 12164841-3424608400-56494@interface-e1000g0#45c8a9d9c8 [7] 2008/07/09 12:06:46: Call Port: 3c2688bd740f-wi7wfa3wkjvo#cf583492ec [7] 2008/07/09 12:06:46: Call Port: 42f6a342@pbx#931656885 [7] 2008/07/09 12:06:46: Call Port: d5cd8888@pbx#1937225949 [9] 2008/07/09 12:06:46: Resolve 38620: aaaa udp 66.23.129.253 5060 [9] 2008/07/09 12:06:46: Resolve 38620: a udp 66.23.129.253 5060 [9] 2008/07/09 12:06:46: Resolve 38620: udp 66.23.129.253 5060 [9] 2008/07/09 12:06:46: SIP Tx udp:66.23.129.253:5060: SIP/2.0 200 Ok Via: SIP/2.0/UDP 66.23.129.253:5060;branch=z9hG4bK4eee.3de6c972.0 Via: SIP/2.0/UDP 69.30.45.229:5061;branch=z9hG4bK1fd93fef3e646235741b1d4c66ac6f10;rport=5061 Record-Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 INVITE Contact: <sip:chambersadvisory@75.150.102.90:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: Bizfon-8000/3.0.0.2933 Content-Type: application/sdp Content-Length: 202 v=0 o=- 573161756 573161756 IN IP4 75.150.102.90 s=- c=IN IP4 75.150.102.90 t=0 0 m=audio 54438 RTP/AVP 0 101 a=rtpmap:0 pcmu/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/07/09 12:06:46: Resolve 38621: tls 192.168.1.71 2058 [9] 2008/07/09 12:06:47: SIP Rx udp:66.23.129.253:5060: ACK sip:chambersadvisory@75.150.102.90:5060;transport=udp SIP/2.0 Record-Route: <sip:chambersadvisory@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> Via: SIP/2.0/UDP 66.23.129.253:5060;branch=0 Via: SIP/2.0/UDP 69.30.45.229:5061;rport=5061;branch=z9hG4bKbc7b1e927ef358a552fcd1ca3480a407 Max-Forwards: 16 From: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 To: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 200 ACK Expires: 300 User-Agent: Sippy [8] 2008/07/09 12:07:02: Packet authenticated by transport layer [9] 2008/07/09 12:07:02: Resolve 38622: tls 192.168.1.233 2097 [8] 2008/07/09 12:07:04: Packet authenticated by transport layer [9] 2008/07/09 12:07:04: Resolve 38623: tls 192.168.1.71 2058 [9] 2008/07/09 12:07:07: Resolve 38624: url sip:66.23.129.253 [9] 2008/07/09 12:07:07: Resolve 38624: udp 66.23.129.253 5060 [8] 2008/07/09 12:07:07: Trunk 2 (nexVortex) has outbound proxy udp:66.23.129.253:5060 [9] 2008/07/09 12:07:07: Resolve 38625: udp 66.23.129.253 5060 [8] 2008/07/09 12:07:07: Answer challenge with username chambersadvisory [9] 2008/07/09 12:07:07: Resolve 38626: udp 66.23.129.253 5060 udp:1 [9] 2008/07/09 12:07:07: Message repetition, packet dropped [8] 2008/07/09 12:07:13: Packet authenticated by transport layer [9] 2008/07/09 12:07:13: Resolve 38627: tls 192.168.1.65 2069 [8] 2008/07/09 12:07:16: Packet authenticated by transport layer [9] 2008/07/09 12:07:16: Resolve 38628: tls 192.168.1.72 2057 [9] 2008/07/09 12:07:17: SIP Rx tls:192.168.1.66:2067: BYE sip:242@192.168.1.2:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.1.66:2054;branch=z9hG4bK-w8q47v1q1glq;rport From: <sip:14135844190@66.23.129.253>;tag=vshqvory73 To: <sip:6038704447@69.30.45.229>;tag=1937225949 Call-ID: d5cd8888@pbx CSeq: 1 BYE Max-Forwards: 70 Contact: <sip:242@192.168.1.66:2054;transport=tls>;flow-id=1 User-Agent: snom360/7.1.30 RTP-RxStat: Total_Rx_Pkts=1550,Rx_Pkts=1550,Rx_Pkts_Lost=0,Remote_Rx_Pkts_Lost=0 RTP-TxStat: Total_Tx_Pkts=1577,Tx_Pkts=1577,Remote_Tx_Pkts=0 Proxy-Require: buttons Content-Length: 0 [9] 2008/07/09 12:07:17: Resolve 38629: tls 192.168.1.66 2067 [9] 2008/07/09 12:07:17: SIP Tx tls:192.168.1.66:2067: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.1.66:2054;branch=z9hG4bK-w8q47v1q1glq;rport=2067 From: <sip:14135844190@66.23.129.253>;tag=vshqvory73 To: <sip:6038704447@69.30.45.229>;tag=1937225949 Call-ID: d5cd8888@pbx CSeq: 1 BYE Contact: <sip:242@192.168.1.2:5061;transport=tls> User-Agent: Bizfon-8000/3.0.0.2933 RTP-RxStat: Dur=37,Pkt=1588,Oct=279488,Underun=0 RTP-TxStat: Dur=32,Pkt=1564,Oct=275264 Content-Length: 0 [7] 2008/07/09 12:07:17: Other Ports: 3 [7] 2008/07/09 12:07:17: Call Port: 12164841-3424608400-56494@interface-e1000g0#45c8a9d9c8 [7] 2008/07/09 12:07:17: Call Port: 3c2688bd740f-wi7wfa3wkjvo#cf583492ec [7] 2008/07/09 12:07:17: Call Port: 42f6a342@pbx#931656885 [9] 2008/07/09 12:07:17: Using outbound proxy sip:192.168.1.71:2058;transport=tls because of flow-label [9] 2008/07/09 12:07:17: Resolve 38630: url sip:192.168.1.71:2058;transport=tls [9] 2008/07/09 12:07:17: Resolve 38630: a tls 192.168.1.71 2058 [9] 2008/07/09 12:07:17: Resolve 38630: tls 192.168.1.71 2058 [9] 2008/07/09 12:07:17: Using outbound proxy sip:192.168.1.66:2067;transport=tls because of flow-label [9] 2008/07/09 12:07:17: Resolve 38631: url sip:192.168.1.66:2067;transport=tls [9] 2008/07/09 12:07:17: Resolve 38631: a tls 192.168.1.66 2067 [9] 2008/07/09 12:07:17: Resolve 38631: tls 192.168.1.66 2067 [9] 2008/07/09 12:07:17: Using outbound proxy sip:192.168.1.72:2057;transport=tls because of flow-label [9] 2008/07/09 12:07:17: Resolve 38632: url sip:192.168.1.72:2057;transport=tls [9] 2008/07/09 12:07:17: Resolve 38632: a tls 192.168.1.72 2057 [9] 2008/07/09 12:07:17: Resolve 38632: tls 192.168.1.72 2057 [9] 2008/07/09 12:07:17: Using outbound proxy sip:192.168.1.10:2056;transport=tls because of flow-label [9] 2008/07/09 12:07:17: Resolve 38633: url sip:192.168.1.10:2056;transport=tls [9] 2008/07/09 12:07:17: Resolve 38633: a tls 192.168.1.10 2056 [9] 2008/07/09 12:07:17: Resolve 38633: tls 192.168.1.10 2056 [9] 2008/07/09 12:07:17: Using outbound proxy sip:192.168.1.65:2069;transport=tls because of flow-label [9] 2008/07/09 12:07:17: Resolve 38634: url sip:192.168.1.65:2069;transport=tls [9] 2008/07/09 12:07:17: Resolve 38634: a tls 192.168.1.65 2069 [9] 2008/07/09 12:07:17: Resolve 38634: tls 192.168.1.65 2069 [9] 2008/07/09 12:07:17: Using outbound proxy sip:192.168.1.233:2097;transport=tls because of flow-label [9] 2008/07/09 12:07:17: Resolve 38635: url sip:192.168.1.233:2097;transport=tls [9] 2008/07/09 12:07:17: Resolve 38635: a tls 192.168.1.233 2097 [9] 2008/07/09 12:07:17: Resolve 38635: tls 192.168.1.233 2097 [9] 2008/07/09 12:07:17: Resolve 38636: url sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on [9] 2008/07/09 12:07:17: Resolve 38636: udp 66.23.129.253 5060 [9] 2008/07/09 12:07:17: SIP Tx udp:66.23.129.253:5060: BYE sip:69.30.45.229:5061 SIP/2.0 Via: SIP/2.0/UDP 75.150.102.90:5060;branch=z9hG4bK-e1a033c9898d59fe272c3887342ac465;rport Route: <sip:14135844190@66.23.129.253:5060;nat=yes;ftag=9176371bbe16666b40160c5ecb1b6cf2;lr=on> From: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 To: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 30383 BYE Max-Forwards: 70 Contact: <sip:chambersadvisory@75.150.102.90:5060;transport=udp> RTP-RxStat: Dur=37,Pkt=1848,Oct=317856,Underun=0 RTP-TxStat: Dur=31,Pkt=1787,Oct=307364 Content-Length: 0 [9] 2008/07/09 12:07:18: SIP Rx udp:66.23.129.253:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 75.150.102.90:5060;branch=z9hG4bK-e1a033c9898d59fe272c3887342ac465;rport=5060 Record-Route: <sip:66.23.129.253:5060;nat=yes;ftag=45c8a9d9c8;lr=on> From: <sip:14135844190@66.23.129.253>;tag=45c8a9d9c8 To: <sip:6038704447@69.30.45.229>;tag=9176371bbe16666b40160c5ecb1b6cf2 Call-ID: 12164841-3424608400-56494@interface-e1000g0 CSeq: 30383 BYE Server: Sippy [7] 2008/07/09 12:07:18: Call 12164841-3424608400-56494@interface-e1000g0#45c8a9d9c8: Clear last request [5] 2008/07/09 12:07:18: BYE Response: Terminate 12164841-3424608400-56494@interface-e1000g0 [7] 2008/07/09 12:07:18: Other Ports: 2 [7] 2008/07/09 12:07:18: Call Port: 3c2688bd740f-wi7wfa3wkjvo#cf583492ec [7] 2008/07/09 12:07:18: Call Port: 42f6a342@pbx#931656885

It was the dial plan. I thought I had a matching rule in there, but it didn't.

I am having a problem with the Outlook TAPI addon. When I initiate a call from outlook, my phone rings, I get that nice recording saying to press 1, then the call disconnects when I press 1. The phone is a Snom 370(7.1.30). [8] 2008/01/04 10:15:58: Packet authenticated by transport layer [9] 2008/01/04 10:15:58: Resolve destination 132: tls 192.168.100.107 3001 [8] 2008/01/04 10:16:06: Packet authenticated by transport layer [9] 2008/01/04 10:16:06: Resolve destination 133: tls 192.168.100.108 3245 [8] 2008/01/04 10:16:08: Packet authenticated by transport layer [9] 2008/01/04 10:16:08: Resolve destination 134: tls 12.25.0.88 3216 [9] 2008/01/04 10:16:09: Message repetition, packet dropped [9] 2008/01/04 10:16:09: Resolve destination 135: aaaa udp 192.168.100.53 1102 [9] 2008/01/04 10:16:09: Resolve destination 135: a udp 192.168.100.53 1102 [9] 2008/01/04 10:16:09: Resolve destination 135: udp 192.168.100.53 1102 [9] 2008/01/04 10:16:09: Resolve destination 136: aaaa udp 192.168.100.53 1102 [9] 2008/01/04 10:16:09: Resolve destination 136: a udp 192.168.100.53 1102 [9] 2008/01/04 10:16:09: Resolve destination 136: udp 192.168.100.53 1102 [7] 2008/01/04 10:16:09: UDP: Opening socket on port 50474 [7] 2008/01/04 10:16:09: UDP: Opening socket on port 50475 [7] 2008/01/04 10:16:09: UDPv6: Opening socket on port 50474 [7] 2008/01/04 10:16:09: UDPv6: Opening socket on port 50475 [9] 2008/01/04 10:16:09: Using outbound proxy sip:192.168.100.57:3382;transport=tls because of flow-label [9] 2008/01/04 10:16:09: Resolve destination 137: url sip:192.168.100.57:3382;transport=tls [9] 2008/01/04 10:16:09: Resolve destination 137: a tls 192.168.100.57 3382 [9] 2008/01/04 10:16:09: Resolve destination 137: tls 192.168.100.57 3382 [9] 2008/01/04 10:16:09: SIP Tx tls:192.168.100.57:3382: INVITE sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d SIP/2.0 Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-40cd877548fe802f2e119438d4baf560;rport From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost> Call-ID: eff78b9e@pbx CSeq: 1240 INVITE Max-Forwards: 70 Contact: <sip:4447@192.168.100.48:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/2.1.4.2345 Alert-Info: <http://127.0.0.1/Bellcore-dr2> P-Asserted-Identity: "Martin Abbott" <sip:4447@localhost> Content-Type: application/sdp Content-Length: 435 v=0 o=- 1256577973 1256577973 IN IP4 192.168.100.48 s=- c=IN IP4 192.168.100.48 t=0 0 m=audio 50474 RTP/AVP 0 8 9 18 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:Ijqed5GeN3QCHWMzAabgn5Y/hx5KcGqwSMVlcl6i a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [9] 2008/01/04 10:16:09: SIP Rx tls:192.168.100.57:3382: SIP/2.0 180 Ringing Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-40cd877548fe802f2e119438d4baf560;rport=5061 From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost>;tag=00knnefwxq Call-ID: eff78b9e@pbx CSeq: 1240 INVITE Contact: <sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d>;flow-id=1 Require: 100rel RSeq: 1 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Content-Length: 0 [9] 2008/01/04 10:16:09: Resolve destination 138: url sip:192.168.100.57:3382;transport=tls [9] 2008/01/04 10:16:09: Resolve destination 138: a tls 192.168.100.57 3382 [9] 2008/01/04 10:16:09: Resolve destination 138: tls 192.168.100.57 3382 [9] 2008/01/04 10:16:09: SIP Tx tls:192.168.100.57:3382: PRACK sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d SIP/2.0 Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-0d938d1093e09090ab5044c5b5b816dd;rport From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost>;tag=00knnefwxq Call-ID: eff78b9e@pbx CSeq: 1241 PRACK Max-Forwards: 70 Contact: <sip:4447@192.168.100.48:5061;transport=tls> RAck: 1 1240 INVITE P-Asserted-Identity: "Martin Abbott" <sip:4447@localhost> Content-Length: 0 [5] 2008/01/04 10:16:09: Not setting dialog state of non-existing call port (call-id=0246f144@pbx#1391040173) [9] 2008/01/04 10:16:09: SIP Rx tls:192.168.100.57:3382: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-0d938d1093e09090ab5044c5b5b816dd;rport=5061 From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost>;tag=00knnefwxq Call-ID: eff78b9e@pbx CSeq: 1241 PRACK Contact: <sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d>;flow-id=1 Content-Length: 0 [7] 2008/01/04 10:16:09: Call eff78b9e@pbx#693009253: Clear last request [9] 2008/01/04 10:16:11: SIP Rx tls:192.168.100.57:3382: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-40cd877548fe802f2e119438d4baf560;rport=5061 From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost>;tag=00knnefwxq Call-ID: eff78b9e@pbx CSeq: 1240 INVITE Contact: <sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d>;flow-id=1 User-Agent: snom370/7.1.30 Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, callerid Content-Type: application/sdp Content-Length: 443 v=0 o=root 2104090577 2104090578 IN IP4 192.168.100.57 s=call c=IN IP4 192.168.100.57 t=0 0 m=audio 59060 RTP/AVP 0 8 9 18 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:G4uHK2dF0qE2Rjg7ePlenOtrwr3jKm2WIRzRvlzn a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:9 g722/8000 a=rtpmap:18 g729/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=encryption:optional a=sendrecv [7] 2008/01/04 10:16:11: Call eff78b9e@pbx#693009253: Clear last INVITE [9] 2008/01/04 10:16:11: Resolve destination 139: url sip:192.168.100.57:3382;transport=tls [9] 2008/01/04 10:16:11: Resolve destination 139: a tls 192.168.100.57 3382 [9] 2008/01/04 10:16:11: Resolve destination 139: tls 192.168.100.57 3382 [9] 2008/01/04 10:16:11: SIP Tx tls:192.168.100.57:3382: ACK sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d SIP/2.0 Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-d15abd3f5de36cc36cf55e0dd3154d48;rport From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost>;tag=00knnefwxq Call-ID: eff78b9e@pbx CSeq: 1240 ACK Max-Forwards: 70 Contact: <sip:4447@192.168.100.48:5061;transport=tls> P-Asserted-Identity: "Martin Abbott" <sip:4447@localhost> Content-Length: 0 [9] 2008/01/04 10:16:13: Resolve destination 140: url sip:192.168.100.57:3382;transport=tls [9] 2008/01/04 10:16:13: Resolve destination 140: a tls 192.168.100.57 3382 [9] 2008/01/04 10:16:13: Resolve destination 140: tls 192.168.100.57 3382 [9] 2008/01/04 10:16:13: SIP Tx tls:192.168.100.57:3382: BYE sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d SIP/2.0 Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-1097b81e192b468ddd89842540ff952d;rport From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost>;tag=00knnefwxq Call-ID: eff78b9e@pbx CSeq: 1242 BYE Max-Forwards: 70 Contact: <sip:4447@192.168.100.48:5061;transport=tls> RTP-RxStat: Dur=4,Pkt=90,Oct=15372,Underun=0 RTP-TxStat: Dur=2,Pkt=89,Oct=15664 P-Asserted-Identity: "Martin Abbott" <sip:4447@localhost> Content-Length: 0 [9] 2008/01/04 10:16:13: Using outbound proxy sip:192.168.100.53:1102;transport=udp because of flow-label [9] 2008/01/04 10:16:13: Resolve destination 141: url sip:192.168.100.53:1102;transport=udp [9] 2008/01/04 10:16:13: Resolve destination 141: a udp 192.168.100.53 1102 [9] 2008/01/04 10:16:13: Resolve destination 141: udp 192.168.100.53 1102 [9] 2008/01/04 10:16:13: Resolve destination 142: aaaa udp 192.168.100.53 1102 [9] 2008/01/04 10:16:13: Resolve destination 142: a udp 192.168.100.53 1102 [9] 2008/01/04 10:16:13: Resolve destination 142: udp 192.168.100.53 1102 [9] 2008/01/04 10:16:13: SIP Rx tls:192.168.100.57:3382: SIP/2.0 200 OK Via: SIP/2.0/TLS 192.168.100.48:5061;branch=z9hG4bK-1097b81e192b468ddd89842540ff952d;rport=5061 From: <sip:4447@localhost>;tag=693009253 To: <sip:16038709400@localhost>;tag=00knnefwxq Call-ID: eff78b9e@pbx CSeq: 1242 BYE Contact: <sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d>;flow-id=1 User-Agent: snom370/7.1.30 RTP-RxStat: Total_Rx_Pkts=93,Rx_Pkts=93,Rx_Pkts_Lost=1,Remote_Rx_Pkts_Lost=0 RTP-TxStat: Total_Tx_Pkts=87,Tx_Pkts=87,Remote_Tx_Pkts=0 Content-Length: 0 [7] 2008/01/04 10:16:13: Call eff78b9e@pbx#693009253: Clear last request [5] 2008/01/04 10:16:13: BYE Response: Terminate eff78b9e@pbx [8] 2008/01/04 10:16:17: Packet authenticated by transport layer [9] 2008/01/04 10:16:17: Resolve destination 143: tls 192.168.100.107 3001 [8] 2008/01/04 10:16:17: Packet authenticated by transport layer [9] 2008/01/04 10:16:17: Resolve destination 144: tls 192.168.100.107 3001 [8] 2008/01/04 10:16:17: Packet authenticated by transport layer [9] 2008/01/04 10:16:17: Resolve destination 145: tls 192.168.100.107 3001 [8] 2008/01/04 10:16:17: Packet authenticated by transport layer [9] 2008/01/04 10:16:17: Resolve destination 146: tls 192.168.100.107 3001 [8] 2008/01/04 10:16:17: Packet authenticated by transport layer [9] 2008/01/04 10:16:17: Resolve destination 147: tls 192.168.100.107 3001 [9] 2008/01/04 10:16:18: SIP Rx tls:192.168.100.57:3382: SUBSCRIBE sip:8201@localhost;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.100.57:1034;branch=z9hG4bK-xv3ouom8mpcy;rport From: <sip:4447@localhost>;tag=n5mj6iqqf0 To: <sip:8201@localhost;user=phone>;tag=9105db35c6 Call-ID: 3c2a64b912e7-4dtu2es60pi6 CSeq: 310 SUBSCRIBE Max-Forwards: 70 Contact: <sip:4447@192.168.100.57:1034;transport=tls;line=g2b2if3d>;flow-id=1 Event: dialog Accept: application/dialog-info+xml User-Agent: snom370/7.1.30 Proxy-Require: buttons Expires: 3600 Content-Length: 0 [8] 2008/01/04 10:16:18: Packet authenticated by transport layer [9] 2008/01/04 10:16:18: Resolve destination 148: tls 192.168.100.57 3382 [9] 2008/01/04 10:16:18: SIP Tx tls:192.168.100.57:3382: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.100.57:1034;branch=z9hG4bK-xv3ouom8mpcy;rport=3382 From: <sip:4447@localhost>;tag=n5mj6iqqf0 To: <sip:8201@localhost;user=phone>;tag=9105db35c6 Call-ID: 3c2a64b912e7-4dtu2es60pi6 CSeq: 310 SUBSCRIBE Contact: <sip:192.168.100.48:5061;transport=tls> Expires: 180 Content-Length: 0

I have done some testing and can confirm it is the CDR and performance emails. If I have either one of them enabled it will crash when it trys to send the mail. If I enable logging to file system with either of the emails enabled, I get the email successfully and it doesn't crash.

We are experiencing this as well in the Debian build. This happens every night around midnight. We ran pbxnsip with strace here is the output from that. We will run it with logging to file system tonight and get those logs to you tomorrow. [pid 17736] clock_gettime(CLOCK_REALTIME, {1198904700, 180985359}) = 0 [pid 17736] futex(0xb7c731b4, FUTEX_WAIT, 223075, {0, 199791033} <unfinished ...> [pid 17739] futex(0xb64803a0, FUTEX_WAKE, 1) = 0 [pid 17739] time(NULL) = 1198904700 [pid 17739] clock_gettime(CLOCK_MONOTONIC, {2464512, 83784957}) = 0 [pid 17739] clock_gettime(CLOCK_MONOTONIC, {2464512, 84030009}) = 0 [pid 17739] clock_gettime(CLOCK_REALTIME, {1198904700, 182720822}) = 0 [pid 17739] clock_gettime(CLOCK_REALTIME, {1198904700, 182937026}) = 0 [pid 17739] futex(0xb6480374, FUTEX_WAIT, 30167, {0, 367783796} <unfinished ...> [pid 17736] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 17736] futex(0xb7c731e0, FUTEX_WAKE, 1) = 0 [pid 17736] clock_gettime(CLOCK_REALTIME, {1198904700, 390701567}) = 0 [pid 17736] clock_gettime(CLOCK_REALTIME, {1198904700, 390911796}) = 0 [pid 17736] futex(0xb7c731b4, FUTEX_WAIT, 223077, {0, 199789771} <unfinished ...> [pid 17739] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out) [pid 17739] futex(0xb64803a0, FUTEX_WAKE, 1) = 0 [pid 17739] clock_gettime(CLOCK_MONOTONIC, {2464512, 462282156}) = 0 [pid 17739] mmap2(NULL, 1894846464, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x3f7ef000 [pid 17739] --- SIGSEGV (Segmentation fault) @ 0 (0) --- Process 17735 detached