Jump to content

centrix-voip

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by centrix-voip

  1. By default, the device only has g711 codec. In case we would like to have G729 license on our unit. What procedure will we need to do?
  2. After identifying DID numbers for each FXO in PSTN gateway, I'm able to differentiate the incoming between these two lines. Thx.
  3. We have two phone lines connected to the cs410 and both of them will go to our hunt group. We configure three polycom phones that have line 1 for hunt group 100 and line 2 for hunt group 200. Is there any way to configure the inbound calls from FXO1 going to hunt group 100 and from FXO2 going to hunt group 200? This way we will know that the inbound call is coming from which PSTN lines. The reason is we would like to know whether the call is coming from our customer or our internal people. Since we always give line 1's phone number (FXO1) for our customer and line 2's phone number (FXO2) for our internal people.
  4. Thanks. The codec problem is because I change the codec preference to be g729 (18) only and our box doesn't have license. After I change it back to g711ulaw (0), I don't see that codec error anymore.
  5. We have install 4 Polycom Soudpoint IP 550 in our company. Periodically, we are seeing 500 internal error message from Polycom Phones and we don't know what is causing that. Here is the logfile we are seeing the error message. [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.7:5060: INVITE sip:204@192.168.2.7 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-3b30df1f145455bd87f731bed4eee735;rport From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1117238412 To: <sip:5086602732@localhost;user=phone> Call-ID: 36f05f17@pbx CSeq: 25473 INVITE Max-Forwards: 70 Contact: <sip:204@192.168.2.200:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.0.0.2914 Content-Type: application/sdp Content-Length: 178 v=0 o=- 252482389 252482389 IN IP4 192.168.2.200 s=- c=IN IP4 192.168.2.200 t=0 0 m=audio 51614 RTP/AVP 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=sendrecv [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.7:5060: NOTIFY sip:204@192.168.2.7 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-0e33958246446e6b735fadef61158be4;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 CSeq: 8393 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="694" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.49:5060: NOTIFY sip:201@192.168.2.49 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-bded669092b5ef5495f718c44b841c62;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 CSeq: 9633 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=288 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="694" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.54:5060: NOTIFY sip:202@192.168.2.54 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-cfc674ae61c354b60fe0043552ac7542;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 CSeq: 23131 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=205 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="688" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.202:5060: NOTIFY sip:203@192.168.2.202 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-91b40f7c514aa805943bd331a1508eca;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 CSeq: 19990 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="688" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.49:5060: SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-a780c8e4e8302dd2ef04760ca2ef7ce1;rport From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1864310274 To: <sip:5086602732@localhost;user=phone>;tag=EEE3B317-BEAB1E1E CSeq: 31103 INVITE Call-ID: 957853cf@pbx Contact: <sip:201@192.168.2.49> User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.49:5060: ACK sip:201@192.168.2.49 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-a780c8e4e8302dd2ef04760ca2ef7ce1;rport From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1864310274 To: <sip:5086602732@localhost;user=phone>;tag=EEE3B317-BEAB1E1E Call-ID: 957853cf@pbx CSeq: 31103 ACK Max-Forwards: 70 Contact: <sip:201@192.168.2.200:5060;transport=udp> Content-Length: 0 [5] 2008/06/04 13:49:41: INVITE Response: Terminate 957853cf@pbx [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.7:5060: NOTIFY sip:204@192.168.2.7 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-db7e7f4ed8140dcda7ab1efe123076c5;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 CSeq: 8394 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="695" state="full" entity="sip:201@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.49:5060: NOTIFY sip:201@192.168.2.49 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-503dc5924285ee2fdb846022cd3490b5;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 CSeq: 9634 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=288 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="695" state="full" entity="sip:201@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.54:5060: NOTIFY sip:202@192.168.2.54 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-76738d73433e437c35ba2991eb2ad8eb;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 CSeq: 23132 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=205 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="689" state="full" entity="sip:201@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.202:5060: NOTIFY sip:203@192.168.2.202 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-8db86b5231059bcda4cb0fe799d993ef;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 CSeq: 19991 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="689" state="full" entity="sip:201@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.7:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-27fbafa08836f6189eb2ff987ccb1188;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 CSeq: 8391 NOTIFY Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 Contact: <sip:204@192.168.2.7> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.49:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-37ee2e47180f0eee77acdb78ee7ba746;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 CSeq: 9631 NOTIFY Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 Contact: <sip:201@192.168.2.49> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.54:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-ca540328064dead67a16a48b84c20471;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 CSeq: 23129 NOTIFY Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 Contact: <sip:202@192.168.2.54> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.202:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-de13230b3ef4c09862081dbe57d4a529;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 CSeq: 19988 NOTIFY Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 Contact: <sip:203@192.168.2.202> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.54:5060: SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-31b327aa99a9cbf718cd7d6df199d47d;rport From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=898848906 To: <sip:5086602732@localhost;user=phone>;tag=E30ABDE-5FC5BA7D CSeq: 13046 INVITE Call-ID: af42d3bf@pbx Contact: <sip:202@192.168.2.54> User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.54:5060: ACK sip:202@192.168.2.54 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-31b327aa99a9cbf718cd7d6df199d47d;rport From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=898848906 To: <sip:5086602732@localhost;user=phone>;tag=E30ABDE-5FC5BA7D Call-ID: af42d3bf@pbx CSeq: 13046 ACK Max-Forwards: 70 Contact: <sip:202@192.168.2.200:5060;transport=udp> Content-Length: 0 [5] 2008/06/04 13:49:41: INVITE Response: Terminate af42d3bf@pbx [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.7:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-c394c8827c0bcb6c27becc7f40d52942;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 CSeq: 8392 NOTIFY Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 Contact: <sip:204@192.168.2.7> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.7:5060: NOTIFY sip:204@192.168.2.7 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-4278827187a3e769bc09e2d23ba6ac69;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 CSeq: 8395 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="696" state="full" entity="sip:202@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.49:5060: NOTIFY sip:201@192.168.2.49 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-0533075fc777c64e43d6d271e48e000e;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 CSeq: 9635 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=288 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="696" state="full" entity="sip:202@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.54:5060: NOTIFY sip:202@192.168.2.54 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-6df01488702f6317bed9b9afec8f5b7c;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 CSeq: 23133 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=204 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="690" state="full" entity="sip:202@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.202:5060: NOTIFY sip:203@192.168.2.202 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-7d856e4fa198920ae1dce8aba42b03b8;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 CSeq: 19992 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="690" state="full" entity="sip:202@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.49:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-b458b73e628f56c52c64b89c4977f72c;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 CSeq: 9632 NOTIFY Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 Contact: <sip:201@192.168.2.49> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.54:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-df4da5d89c452c72bed2037dd0b9ab89;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 CSeq: 23130 NOTIFY Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 Contact: <sip:202@192.168.2.54> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.7:5060: SIP/2.0 488 Not Acceptable Here Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-3b30df1f145455bd87f731bed4eee735;rport From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1117238412 To: <sip:5086602732@localhost;user=phone>;tag=93F043CB-7143ABF0 CSeq: 25473 INVITE Call-ID: 36f05f17@pbx Contact: <sip:204@192.168.2.7> User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.7:5060: ACK sip:204@192.168.2.7 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-3b30df1f145455bd87f731bed4eee735;rport From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1117238412 To: <sip:5086602732@localhost;user=phone>;tag=93F043CB-7143ABF0 Call-ID: 36f05f17@pbx CSeq: 25473 ACK Max-Forwards: 70 Contact: <sip:204@192.168.2.200:5060;transport=udp> Content-Length: 0 [5] 2008/06/04 13:49:41: INVITE Response: Terminate 36f05f17@pbx [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.7:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-0e33958246446e6b735fadef61158be4;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 CSeq: 8393 NOTIFY Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 Contact: <sip:204@192.168.2.7> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.49:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-bded669092b5ef5495f718c44b841c62;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 CSeq: 9633 NOTIFY Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 Contact: <sip:201@192.168.2.49> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.54:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-cfc674ae61c354b60fe0043552ac7542;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 CSeq: 23131 NOTIFY Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 Contact: <sip:202@192.168.2.54> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.7:5060: NOTIFY sip:204@192.168.2.7 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-200126caaa4e6d4fa6b293b3da9e2a96;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 CSeq: 8396 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="697" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.49:5060: NOTIFY sip:201@192.168.2.49 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-e51a55da3f94a112b4f361b7ebb2837d;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 CSeq: 9636 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=288 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="697" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.54:5060: NOTIFY sip:202@192.168.2.54 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-82a07b62fe2b6c3e985905e15c8c803a;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 CSeq: 23134 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=204 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="691" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tx udp:192.168.2.202:5060: NOTIFY sip:203@192.168.2.202 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-2cf1288a6cf04654e126472f0a58f5d7;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 CSeq: 19993 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="691" state="full" entity="sip:204@localhost"></dialog-info> [5] 2008/06/04 13:49:41: SIP Tr udp:127.0.0.1:5062: SIP/2.0 183 Ringing Via: SIP/2.0/UDP 127.0.0.1:5062 From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1291554098 To: <sip:5086602732@localhost;user=phone>;tag=0f7971ea97 Call-ID: d9cca7b4@fxo CSeq: 1 INVITE Contact: <sip:5086602732@127.0.0.1:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.0.0.2914 Content-Type: application/sdp Content-Length: 182 v=0 o=- 660877821 660877821 IN IP4 127.0.0.1 s=- c=IN IP4 127.0.0.1 t=0 0 m=audio 54162 RTP/AVP 101 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=sendrecv [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.202:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-91b40f7c514aa805943bd331a1508eca;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 CSeq: 19990 NOTIFY Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 Contact: <sip:203@192.168.2.202> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.7:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-db7e7f4ed8140dcda7ab1efe123076c5;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 CSeq: 8394 NOTIFY Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 Contact: <sip:204@192.168.2.7> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.49:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-503dc5924285ee2fdb846022cd3490b5;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 CSeq: 9634 NOTIFY Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 Contact: <sip:201@192.168.2.49> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.54:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-76738d73433e437c35ba2991eb2ad8eb;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 CSeq: 23132 NOTIFY Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 Contact: <sip:202@192.168.2.54> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.202:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-8db86b5231059bcda4cb0fe799d993ef;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 CSeq: 19991 NOTIFY Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 Contact: <sip:203@192.168.2.202> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.7:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-4278827187a3e769bc09e2d23ba6ac69;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 CSeq: 8395 NOTIFY Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 Contact: <sip:204@192.168.2.7> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Tx udp:127.0.0.1:5062: SIP/2.0 487 Request Terminated Via: SIP/2.0/UDP 127.0.0.1:5062 From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1291554098 To: <sip:5086602732@localhost;user=phone>;tag=0f7971ea97 Call-ID: d9cca7b4@fxo CSeq: 1 INVITE Contact: <sip:5086602732@127.0.0.1:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: pbxnsip-PBX/3.0.0.2914 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.49:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-0533075fc777c64e43d6d271e48e000e;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 CSeq: 9635 NOTIFY Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 Contact: <sip:201@192.168.2.49> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.54:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-6df01488702f6317bed9b9afec8f5b7c;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 CSeq: 23133 NOTIFY Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 Contact: <sip:202@192.168.2.54> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.202:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-7d856e4fa198920ae1dce8aba42b03b8;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 CSeq: 19992 NOTIFY Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 Contact: <sip:203@192.168.2.202> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.7:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-200126caaa4e6d4fa6b293b3da9e2a96;rport From: <sip:204@192.168.2.200>;tag=722b7c6bfe To: "204" <sip:204@192.168.2.200>;tag=D6F25FBF-4E8817F4 CSeq: 8396 NOTIFY Call-ID: d288ac18-892a681-bb9fd05e@192.168.2.7 Contact: <sip:204@192.168.2.7> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.49:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-e51a55da3f94a112b4f361b7ebb2837d;rport From: <sip:201@192.168.2.200>;tag=d1ad9cd7a4 To: "201" <sip:201@192.168.2.200>;tag=A209C046-AC3AA951 CSeq: 9636 NOTIFY Call-ID: 243fdf7d-d5e2c86c-30dc705f@192.168.2.49 Contact: <sip:201@192.168.2.49> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: PSTN: Response code: 183 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.54:5060: SIP/2.0 200 OK Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-82a07b62fe2b6c3e985905e15c8c803a;rport From: <sip:202@192.168.2.200>;tag=1dc2c79294 To: "202" <sip:202@192.168.2.200>;tag=627C590C-C7BD95A3 CSeq: 23134 NOTIFY Call-ID: 7e4a0a0f-46317fd2-d98509c1@192.168.2.54 Contact: <sip:202@192.168.2.54> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.202:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-2cf1288a6cf04654e126472f0a58f5d7;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 CSeq: 19993 NOTIFY Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 Contact: <sip:203@192.168.2.202> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0 [5] 2008/06/04 13:49:41: PSTN: Response code: 487 [5] 2008/06/04 13:49:41: SIP Tr udp:192.168.2.202:5060: NOTIFY sip:203@192.168.2.202 SIP/2.0 Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-daf02cdcaacd3f6381afbb52f36e6861;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 CSeq: 19989 NOTIFY Max-Forwards: 70 Contact: <sip:192.168.2.200:5060;transport=udp> Event: dialog Subscription-State: active;expires=289 Content-Type: application/dialog-info+xml Content-Length: 149 <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="687" state="full" entity="sip:202@localhost"></dialog-info> [4] 2008/06/04 13:49:41: PSTN: Call rejected on 1 [5] 2008/06/04 13:49:41: SIP Rx udp:127.0.0.1:5062: ACK sip:5086602732@localhost;user=phone SIP/2.0 Via: SIP/2.0/UDP 127.0.0.1:5062 From: "Anonymous" <sip:anonymous@localhost;user=phone>;tag=1291554098 To: <sip:5086602732@localhost;user=phone> Call-ID: d9cca7b4@fxo Contact: <sip:127.0.0.1:5062> CSeq: 1 ACK Content-Length: 0 [3] 2008/06/04 13:49:41: PSTN: Channel 1: Hangup [5] 2008/06/04 13:49:41: PSTN: Channel 1 goes onhook [5] 2008/06/04 13:49:41: PSTN: enable_callerid 1 [3] 2008/06/04 13:49:41: PSTN: Channel 1 going to GO_ONHOOK [5] 2008/06/04 13:49:41: SIP Rx udp:192.168.2.202:5060: SIP/2.0 500 Internal Server Error Via: SIP/2.0/UDP 192.168.2.200:5060;branch=z9hG4bK-daf02cdcaacd3f6381afbb52f36e6861;rport From: <sip:203@192.168.1.55>;tag=0aea898eff To: "203" <sip:203@192.168.1.55>;tag=67B36DC1-75EF9DA6 CSeq: 19989 NOTIFY Call-ID: 2452c3da-fef2b3cb-7890cee8@192.168.2.202 Contact: <sip:203@192.168.2.202> Event: dialog User-Agent: PolycomSoundPointIP-SPIP_550-UA/2.2.2.0084 Content-Length: 0
×
×
  • Create New...