Erwin Posted June 8, 2010 Report Share Posted June 8, 2010 Hello, I am a complete newbie when it comes to PBX's so please bear with me! Since I often implement OCS 2007 R2 at customer locations but am always reliant on telephony partners for PBX integration I wanted to see if I can get this working by myself, but until now without the desired result. I followed Jan's instructions as far as was possible (by the looks of it, those instructions were made with an older version of PBXNSIP), but I cannot get the Communicator to ring and cannot dial out from the communicator. Using X-lite I can receive calls and dial out using pbxnsip. I am using a sip registration trunk to a betamax clone (Poivy.com). Below is the logging Icurrently receive when there is an incoming call. Can anyone shed some light as to what is going wrong here? (I replaced my own mobile number which is used to call to pbxnsip and my poivy username) Thank you, Erwin [5] 2010/06/05 17:56:39: Last message repeated 10 times [7] 2010/06/05 17:56:39: SIP Rx udp:194.120.0.198:5060: INVITE sip:username@192.168.195.134:5060;transport=udp;line=c81e728d SIP/2.0 Via: SIP/2.0/UDP 194.120.0.198:5060;branch=z9hG4bK29642a25576949b29237ad926579ab5d From: <sip:<mymobileno-replacedbythis>@sip.poivy.com:5060>;tag=c11710acc12b10ac4c050cd81a1203 To: <sip:username@192.168.195.134:5060> Contact: sip:<mymobileno-replacedbythis>@194.120.0.198:5060 Call-ID: c517619025304e6cad45ba0f44a95a3f CSeq: 1 INVITE User-Agent: (Very nice Sip Registrar/Proxy Server) Allow: ACK,BYE,CANCEL,INVITE,REGISTER,OPTIONS,INFO,MESSAGE Content-Type: application/sdp Content-Length: 335 v=0 o=username 1275774997 1275774997 IN IP4 194.221.62.43 s=SIP Call c=IN IP4 194.221.62.43 t=0 0 m=audio 25486 RTP/AVP 8 0 2 18 4 3 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:2 G726-32/8000 a=rtpmap:18 G729/8000 a=fmtp:18 annexb=no a=rtpmap:4 G723/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 [5] 2010/06/05 17:56:39: Identify trunk (line match) 2 [7] 2010/06/05 17:56:39: SIP Tx udp:194.120.0.198:5060: SIP/2.0 100 Trying Via: SIP/2.0/UDP 194.120.0.198:5060;branch=z9hG4bK29642a25576949b29237ad926579ab5d From: <sip:<mymobileno-replacedbythis>@sip.poivy.com:5060>;tag=c11710acc12b10ac4c050cd81a1203 To: <sip:username@192.168.195.134:5060>;tag=6828f03059 Call-ID: c517619025304e6cad45ba0f44a95a3f CSeq: 1 INVITE Content-Length: 0 [6] 2010/06/05 17:56:39: Sending RTP for c517619025304e6cad45ba0f44a95a3f#6828f03059 to 194.221.62.43:25486 [5] 2010/06/05 17:56:39: Domain trunk poivy@pbx.company.com sends call to 40 in domain pbx.company.com [7] 2010/06/05 17:56:39: SIP Tx udp:192.168.195.136:5060: INVITE sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 INVITE Max-Forwards: 70 Contact: <sip:40@192.168.195.134: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/4.0.1.3499 Alert-Info: <http://127.0.0.1/Bellcore-dr3> Content-Type: application/sdp Content-Length: 380 v=0 o=- 11683 11683 IN IP4 192.168.195.134 s=- c=IN IP4 192.168.195.134 t=0 0 m=audio 56732 RTP/AVP 0 8 9 18 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 2010/06/05 17:56:39: Connection refused on udp:192.168.195.136:5060 [6] 2010/06/05 17:56:39: Could not determine destination address on 1185 [7] 2010/06/05 17:56:40: SIP Tr udp:192.168.195.136:5060: INVITE sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 INVITE Max-Forwards: 70 Contact: <sip:40@192.168.195.134: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/4.0.1.3499 Alert-Info: <http://127.0.0.1/Bellcore-dr3> Content-Type: application/sdp Content-Length: 380 v=0 o=- 11683 11683 IN IP4 192.168.195.134 s=- c=IN IP4 192.168.195.134 t=0 0 m=audio 56732 RTP/AVP 0 8 9 18 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2010/06/05 17:56:41: Last message repeated 2 times [5] 2010/06/05 17:56:41: Connection refused on udp:192.168.195.136:5060 [6] 2010/06/05 17:56:41: Could not determine destination address on 1185 [7] 2010/06/05 17:56:43: SIP Tr udp:192.168.195.136:5060: INVITE sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 INVITE Max-Forwards: 70 Contact: <sip:40@192.168.195.134: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/4.0.1.3499 Alert-Info: <http://127.0.0.1/Bellcore-dr3> Content-Type: application/sdp Content-Length: 380 v=0 o=- 11683 11683 IN IP4 192.168.195.134 s=- c=IN IP4 192.168.195.134 t=0 0 m=audio 56732 RTP/AVP 0 8 9 18 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 2010/06/05 17:56:43: Connection refused on udp:192.168.195.136:5060 [6] 2010/06/05 17:56:43: Could not determine destination address on 1185 [7] 2010/06/05 17:56:47: SIP Tr udp:192.168.195.136:5060: INVITE sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 INVITE Max-Forwards: 70 Contact: <sip:40@192.168.195.134: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/4.0.1.3499 Alert-Info: <http://127.0.0.1/Bellcore-dr3> Content-Type: application/sdp Content-Length: 380 v=0 o=- 11683 11683 IN IP4 192.168.195.134 s=- c=IN IP4 192.168.195.134 t=0 0 m=audio 56732 RTP/AVP 0 8 9 18 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 2010/06/05 17:56:47: Connection refused on udp:192.168.195.136:5060 [6] 2010/06/05 17:56:47: Could not determine destination address on 1185 [7] 2010/06/05 17:56:55: SIP Tr udp:192.168.195.136:5060: INVITE sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 INVITE Max-Forwards: 70 Contact: <sip:40@192.168.195.134: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/4.0.1.3499 Alert-Info: <http://127.0.0.1/Bellcore-dr3> Content-Type: application/sdp Content-Length: 380 v=0 o=- 11683 11683 IN IP4 192.168.195.134 s=- c=IN IP4 192.168.195.134 t=0 0 m=audio 56732 RTP/AVP 0 8 9 18 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 2010/06/05 17:56:55: Connection refused on udp:192.168.195.136:5060 [6] 2010/06/05 17:56:55: Could not determine destination address on 1185 [7] 2010/06/05 17:57:11: SIP Tr udp:192.168.195.136:5060: INVITE sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 INVITE Max-Forwards: 70 Contact: <sip:40@192.168.195.134: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/4.0.1.3499 Alert-Info: <http://127.0.0.1/Bellcore-dr3> Content-Type: application/sdp Content-Length: 380 v=0 o=- 11683 11683 IN IP4 192.168.195.134 s=- c=IN IP4 192.168.195.134 t=0 0 m=audio 56732 RTP/AVP 0 8 9 18 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [5] 2010/06/05 17:57:11: Connection refused on udp:192.168.195.136:5060 [6] 2010/06/05 17:57:11: Could not determine destination address on 1185 [5] 2010/06/05 17:57:11: Did not receive ACK, disconnecting call c517619025304e6cad45ba0f44a95a3f [7] 2010/06/05 17:57:11: SIP Tx udp:192.168.195.136:5060: CANCEL sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 CANCEL Max-Forwards: 70 Content-Length: 0 [7] 2010/06/05 17:57:12: SIP Tr udp:192.168.195.136:5060: CANCEL sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 CANCEL Max-Forwards: 70 Content-Length: 0 [5] 2010/06/05 17:57:12: Connection refused on udp:192.168.195.136:5060 [7] 2010/06/05 17:57:12: SIP Tx udp:192.168.195.136:5060: CANCEL sip:+3185785704440@ocs-md.domain.local SIP/2.0 Via: SIP/2.0/UDP 192.168.195.134:5060;branch=z9hG4bK-c4617f755abaa2cc42b18b10a8d3c1fa;rport From: <sip:<mymobileno-replacedbythis>@pbx.company.com:5060>;tag=54322 To: "Forty Zero" <sip:40@pbx.company.com> Call-ID: 63d6bce7@pbx CSeq: 25369 CANCEL Max-Forwards: 70 Content-Length: 0 [6] 2010/06/05 17:57:12: Could not determine destination address on 1185 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.