Telis Ltd Posted December 21, 2010 Report Share Posted December 21, 2010 Hi, I'd really appreciate some help. I am evaluating the SNOM ONE as an alternative to 3CX for our customers. I have installed the system and used the default pbx.company.com that the system comes pre-confgiured with. Just by changing the DHCP 66 option I was able to provision my SNOM handsets and was making calls between handsets within minutes, and configuring BLF keys minutes later. The problems started whilst trying to set up Trunks/Dial Plans to make outgoing calls (or receive incoming calls). I have SIP accounts in the UK with Gradwell and Sipgate Team but I haven't been able to get either of them work despite trying for almost 2 days. They are SIP accounts not SIP trunks and they have all worked when directly configured on the SNOM handsets themselves. OK first is sipgate. The trunk is:- # Trunk 2 in domain pbx.company.com Name: sipgate Type: register To: sip RegPass: ******** Direction: Disabled: false Global: false Display: sipgate RegAccount: 113XXXXXX RegRegistrar: sipgate.co.uk RegKeep: RegUser: 113XXXXXX Icid: Require: OutboundProxy: proxy.live.sipgate.co.uk Ani: DialExtension: Prefix: Trusted: false AcceptRedirect: false RfcRtp: false Analog: false SendEmail: UseUuid: false Ring180: false Failover: never Privacy: pai Glob: RequestTimeout: Codecs: CodecLock: true Expires: 3600 FromUser: 11336XXXX@sipgate.co.uk Tel: true TranscodeDtmf: false AssociatedAddresses: InterOffice: false DialPlan: Colines: DialogPermission: The error I currently get is "forbidden (check from field) 07957 XXXXXX" The log is:- [7] 2010/12/21 16:39:20: SIP Rx tls:192.168.248.37:2518: INVITE sip:07957XXXXXX@pbx.company.com;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-a27bjjeksxun;rport From: "Forty One" <sip:41@pbx.company.com>;tag=2mmlr9hspj To: <sip:07957XXXXXX@pbx.company.com;user=phone> Call-ID: 3c2ba3119dff-92nvxjpsmggu CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz>;reg-id=1 X-Serialnumber: 0004132612C1 P-Key-Flags: resolution="31x13", keys="4" User-Agent: snom370/8.4.18 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, from-change Session-Expires: 3600;refresher=uas Min-SE: 90 Proxy-Require: buttons Content-Type: application/sdp Content-Length: 528 v=0 o=root 1825897844 1825897844 IN IP4 192.168.248.37 s=call c=IN IP4 192.168.248.37 t=0 0 m=audio 56658 RTP/AVP 9 0 8 2 3 18 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:oMorpS60MeiCMRwQHQ30L1G9o0KbpgWMnf7UWAro a=rtpmap:9 g722/8000 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:4 g723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendrecv [7] 2010/12/21 16:39:20: SIP Tx tls:192.168.248.37:2518: SIP/2.0 100 Trying Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-a27bjjeksxun;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=2mmlr9hspj To: <sip:07957XXXXXX@pbx.company.com;user=phone>;tag=7f336de145 Call-ID: 3c2ba3119dff-92nvxjpsmggu CSeq: 1 INVITE Content-Length: 0 [7] 2010/12/21 16:39:20: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-92758490d53e30ce14a37d58141e784e;rport From: "Forty One" <sip:41@pbx.company.com>;tag=13586 To: "Forty One" <sip:41@pbx.company.com> Call-ID: 5y2k99gb@pbx CSeq: 40865 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [7] 2010/12/21 16:39:20: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-67b5aa292419d8e13aa451bdbad2f41c;rport From: "Forty One" <sip:41@pbx.company.com>;tag=6530 To: "Forty One" <sip:41@pbx.company.com> Call-ID: 1xlvjm1q@pbx CSeq: 54936 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [7] 2010/12/21 16:39:20: SIP Tx udp:217.10.68.149:5060: INVITE sip:07957XXXXXX@sipgate.co.uk;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-998e88eaeaf4307abc7f9ec7ca0ad805;rport From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=29161 To: <sip:07957XXXXXX@sipgate.co.uk;user=phone> Call-ID: 11c2ad2f@pbx CSeq: 7598 INVITE Max-Forwards: 70 Contact: <sip:11336XXXX@192.168.248.140:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 P-Asserted-Identity: "sipgate" <sip:11336XXXX@sipgate.co.uk> Content-Type: application/sdp Content-Length: 333 v=0 o=- 14430 14430 IN IP4 192.168.248.140 s=- c=IN IP4 192.168.248.140 t=0 0 m=audio 55960 RTP/AVP 0 8 9 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2010/12/21 16:39:20: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-84a48b09a5642ba65a1ce74ce680e147;rport From: "Forty One" <sip:41@pbx.company.com>;tag=26520 To: "Forty One" <sip:41@pbx.company.com> Call-ID: z1h0dybk@pbx CSeq: 43155 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 20 k=4 c=on x=ext [7] 2010/12/21 16:39:20: SIP Tx tls:192.168.248.37:2518: SIP/2.0 183 Session Progress Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-a27bjjeksxun;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=2mmlr9hspj To: <sip:07957XXXXXX@pbx.company.com;user=phone>;tag=7f336de145 Call-ID: 3c2ba3119dff-92nvxjpsmggu CSeq: 1 INVITE Contact: <sip:41@192.168.248.140:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 Require: 100rel RSeq: 1 Content-Type: application/sdp Content-Length: 429 v=0 o=- 48940 48940 IN IP4 192.168.248.140 s=- c=IN IP4 192.168.248.140 t=0 0 m=audio 52024 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:trVCEiSDAmbSmjqsckttnnNUXic3YISKDpeDbdD+ 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=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2010/12/21 16:39:20: SIP Rx udp:217.10.68.149:5060: SIP/2.0 407 Proxy Authentication Required Via: SIP/2.0/UDP 192.168.248.140:5060;received=188.220.16.126;branch=z9hG4bK-998e88eaeaf4307abc7f9ec7ca0ad805;rport=46788 From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=29161 To: <sip:07957XXXXXX@sipgate.co.uk;user=phone>;tag=efae1b206a1df22b5fbc395b5a747d13.93f5 Call-ID: 11c2ad2f@pbx CSeq: 7598 INVITE Proxy-Authenticate: Digest realm="sipgate.co.uk", nonce="4d10d9641f69f83c1fc040284b6db20367e43dee" Content-Length: 0 [7] 2010/12/21 16:39:20: SIP Tx udp:217.10.68.149:5060: ACK sip:07957XXXXXX@sipgate.co.uk;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-998e88eaeaf4307abc7f9ec7ca0ad805;rport From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=29161 To: <sip:07957XXXXXX@sipgate.co.uk;user=phone>;tag=efae1b206a1df22b5fbc395b5a747d13.93f5 Call-ID: 11c2ad2f@pbx CSeq: 7598 ACK Max-Forwards: 70 Content-Length: 0 [7] 2010/12/21 16:39:20: SIP Tx udp:217.10.68.149:5060: INVITE sip:07957XXXXXX@sipgate.co.uk;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-80c1b309f772ef9d1a6330a5ee6bbd13;rport From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=29161 To: <sip:07957XXXXXX@sipgate.co.uk;user=phone> Call-ID: 11c2ad2f@pbx CSeq: 7599 INVITE Max-Forwards: 70 Contact: <sip:11336XXXX@192.168.248.140:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 P-Asserted-Identity: "sipgate" <sip:11336XXXX@sipgate.co.uk> Proxy-Authorization: Digest realm="sipgate.co.uk",nonce="4d10d9641f69f83c1fc040284b6db20367e43dee",response="c093700bf2faca5bdcf8bc09beeb059d",username="11336XXXX",uri="sip:07957XXXXXX@sipgate.co.uk;user=phone",algorithm=MD5 Content-Type: application/sdp Content-Length: 333 v=0 o=- 14430 14430 IN IP4 192.168.248.140 s=- c=IN IP4 192.168.248.140 t=0 0 m=audio 55960 RTP/AVP 0 8 9 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2010/12/21 16:39:21: SIP Tr udp:217.10.68.149:5060: INVITE sip:07957XXXXXX@sipgate.co.uk;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-80c1b309f772ef9d1a6330a5ee6bbd13;rport From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=29161 To: <sip:07957XXXXXX@sipgate.co.uk;user=phone> Call-ID: 11c2ad2f@pbx CSeq: 7599 INVITE Max-Forwards: 70 Contact: <sip:11336XXXX@192.168.248.140:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 P-Asserted-Identity: "sipgate" <sip:11336XXXX@sipgate.co.uk> Proxy-Authorization: Digest realm="sipgate.co.uk",nonce="4d10d9641f69f83c1fc040284b6db20367e43dee",response="c093700bf2faca5bdcf8bc09beeb059d",username="11336XXXX",uri="sip:07957XXXXXX@sipgate.co.uk;user=phone",algorithm=MD5 Content-Type: application/sdp Content-Length: 333 v=0 o=- 14430 14430 IN IP4 192.168.248.140 s=- c=IN IP4 192.168.248.140 t=0 0 m=audio 55960 RTP/AVP 0 8 9 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2010/12/21 16:39:21: SIP Rx udp:217.10.68.149:5060: SIP/2.0 403 Forbidden (check from field) Via: SIP/2.0/UDP 192.168.248.140:5060;received=188.220.16.126;branch=z9hG4bK-80c1b309f772ef9d1a6330a5ee6bbd13;rport=46788 From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=29161 To: <sip:07957XXXXXX@sipgate.co.uk;user=phone>;tag=efae1b206a1df22b5fbc395b5a747d13.2ba2 Call-ID: 11c2ad2f@pbx CSeq: 7599 INVITE Content-Length: 0 [7] 2010/12/21 16:39:21: Call 11c2ad2f@pbx: Clear last INVITE [7] 2010/12/21 16:39:21: SIP Tx udp:217.10.68.149:5060: ACK sip:07957XXXXXX@sipgate.co.uk;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-80c1b309f772ef9d1a6330a5ee6bbd13;rport From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=29161 To: <sip:07957XXXXXX@sipgate.co.uk;user=phone>;tag=efae1b206a1df22b5fbc395b5a747d13.2ba2 Call-ID: 11c2ad2f@pbx CSeq: 7599 ACK Max-Forwards: 70 Contact: <sip:11336XXXX@192.168.248.140:5060;transport=udp> P-Asserted-Identity: "sipgate" <sip:11336XXXX@sipgate.co.uk> Content-Length: 0 [5] 2010/12/21 16:39:21: INVITE Response 403 Forbidden (check from field): Terminate 11c2ad2f@pbx [7] 2010/12/21 16:39:21: SIP Tx tls:192.168.248.37:2518: SIP/2.0 403 Forbidden (check from field) Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-a27bjjeksxun;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=2mmlr9hspj To: <sip:07957XXXXXX@pbx.company.com;user=phone>;tag=7f336de145 Call-ID: 3c2ba3119dff-92nvxjpsmggu CSeq: 1 INVITE Contact: <sip:41@192.168.248.140:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 Content-Length: 0 [7] 2010/12/21 16:39:21: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-92758490d53e30ce14a37d58141e784e;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=13586 To: "Forty One" <sip:41@pbx.company.com> Call-ID: 5y2k99gb@pbx CSeq: 40865 MESSAGE Content-Length: 0 [7] 2010/12/21 16:39:21: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-67b5aa292419d8e13aa451bdbad2f41c;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=6530 To: "Forty One" <sip:41@pbx.company.com> Call-ID: 1xlvjm1q@pbx CSeq: 54936 MESSAGE Content-Length: 0 [7] 2010/12/21 16:39:21: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-84a48b09a5642ba65a1ce74ce680e147;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=26520 To: "Forty One" <sip:41@pbx.company.com> Call-ID: z1h0dybk@pbx CSeq: 43155 MESSAGE Content-Length: 0 [7] 2010/12/21 16:39:21: SIP Rx tls:192.168.248.37:2518: PRACK sip:41@192.168.248.140:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-jff9tkln4bxf;rport From: "Forty One" <sip:41@pbx.company.com>;tag=2mmlr9hspj To: <sip:07957XXXXXX@pbx.company.com;user=phone>;tag=7f336de145 Call-ID: 3c2ba3119dff-92nvxjpsmggu CSeq: 2 PRACK Max-Forwards: 70 Contact: <sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz>;reg-id=1 RAck: 1 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Proxy-Require: buttons Content-Length: 0 [7] 2010/12/21 16:39:21: SIP Tx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-jff9tkln4bxf;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=2mmlr9hspj To: <sip:07957XXXXXX@pbx.company.com;user=phone>;tag=7f336de145 Call-ID: 3c2ba3119dff-92nvxjpsmggu CSeq: 2 PRACK Contact: <sip:41@192.168.248.140:5061;transport=tls> User-Agent: snom-PBX/4.2.0.3950 Content-Length: 0 [7] 2010/12/21 16:39:22: SIP Rx tls:192.168.248.37:2518: ACK sip:07957XXXXXX@pbx.company.com;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-a27bjjeksxun;rport From: "Forty One" <sip:41@pbx.company.com>;tag=2mmlr9hspj To: <sip:07957XXXXXX@pbx.company.com;user=phone>;tag=7f336de145 Call-ID: 3c2ba3119dff-92nvxjpsmggu CSeq: 1 ACK Max-Forwards: 70 Contact: <sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz>;reg-id=1 Proxy-Require: buttons Content-Length: 0 [7] 2010/12/21 16:39:22: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-4a8c76467ac4952638593def9ceae63a;rport From: "Forty One" <sip:41@pbx.company.com>;tag=6984 To: "Forty One" <sip:41@pbx.company.com> Call-ID: 2wl6w6l5@pbx CSeq: 19370 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [7] 2010/12/21 16:39:22: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-592b0baba1671ef9e23b3a92afffb249;rport From: "Forty One" <sip:41@pbx.company.com>;tag=27747 To: "Forty One" <sip:41@pbx.company.com> Call-ID: fo9v5afq@pbx CSeq: 22038 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [7] 2010/12/21 16:39:22: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-4a8c76467ac4952638593def9ceae63a;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=6984 To: "Forty One" <sip:41@pbx.company.com> Call-ID: 2wl6w6l5@pbx CSeq: 19370 MESSAGE Content-Length: 0 [7] 2010/12/21 16:39:23: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-592b0baba1671ef9e23b3a92afffb249;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=27747 To: "Forty One" <sip:41@pbx.company.com> Call-ID: fo9v5afq@pbx CSeq: 22038 MESSAGE Content-Length: 0 [7] 2010/12/21 16:39:23: SIP Rx tls:192.168.248.32:3501: SUBSCRIBE sip:42@pbx.company.com;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.248.32:3501;branch=z9hG4bK-fbbdhowqxwml;rport From: <sip:42@pbx.company.com>;tag=ki6jvpvr2x To: <sip:42@pbx.company.com;user=phone> Call-ID: 3c2ba30a6b88-0co1uigffbus CSeq: 2983 SUBSCRIBE Max-Forwards: 70 Contact: <sip:42@192.168.248.32:3501;transport=tls;line=xdtdbgrm>;reg-id=1 Event: message-summary Accept: application/simple-message-summary User-Agent: snom320/8.4.18 Proxy-Require: buttons Expires: 3600 Content-Length: 0 [7] 2010/12/21 16:39:23: SIP Tx tls:192.168.248.32:3501: SIP/2.0 404 Not Found Via: SIP/2.0/TLS 192.168.248.32:3501;branch=z9hG4bK-fbbdhowqxwml;rport=3501 From: <sip:42@pbx.company.com>;tag=ki6jvpvr2x To: <sip:42@pbx.company.com;user=phone>;tag=e0387eef05 Call-ID: 3c2ba30a6b88-0co1uigffbus CSeq: 2983 SUBSCRIBE Content-Length: 0 With Gradwell:- Trunk:- # Trunk 3 in domain pbx.company.com Name: Gradwell Type: register To: sip RegPass: ******** Direction: Disabled: false Global: false Display: Gradwell (Chris) RegAccount: 205XXX RegRegistrar: sip.gradwell.net RegKeep: RegUser: 205XXX Icid: Require: OutboundProxy: nat.gradwell.net Ani: DialExtension: Prefix: Trusted: false AcceptRedirect: false RfcRtp: false Analog: false SendEmail: UseUuid: false Ring180: false Failover: never Privacy: pai Glob: RequestTimeout: Codecs: CodecLock: true Expires: 3600 FromUser: Tel: true TranscodeDtmf: false AssociatedAddresses: InterOffice: false DialPlan: Colines: DialogPermission: Error Message is:- "Forbidden - no OBP 07957XXXXXX" Here is the log:- [7] 2010/12/21 17:38:45: SIP Rx tls:192.168.248.32:3558: REGISTER sip:pbx.company.com SIP/2.0 Via: SIP/2.0/TLS 192.168.248.32:3558;branch=z9hG4bK-rzzp3kkqs3d1;rport From: "Forty Two" <sip:42@pbx.company.com>;tag=edh9n3voik To: "Forty Two" <sip:42@pbx.company.com> Call-ID: 3c2670249af1-bi3qpnp77vpo CSeq: 7078 REGISTER Max-Forwards: 70 Contact: <sip:42@192.168.248.32:3558;transport=tls;line=xdtdbgrm>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:a9c7202a-7651-4857-bad0-2b032eb6bfc7>" User-Agent: snom320/8.4.18 Allow-Events: dialog X-Real-IP: 192.168.248.32 Supported: path, gruu WWW-Contact: <http://192.168.248.32:80> WWW-Contact: <https://192.168.248.32:443> Proxy-Require: buttons Expires: 900 Content-Length: 0 [7] 2010/12/21 17:38:45: SIP Tx tls:192.168.248.32:3558: SIP/2.0 404 Not Found Via: SIP/2.0/TLS 192.168.248.32:3558;branch=z9hG4bK-rzzp3kkqs3d1;rport=3558 From: "Forty Two" <sip:42@pbx.company.com>;tag=edh9n3voik To: "Forty Two" <sip:42@pbx.company.com>;tag=8f8c74519b Call-ID: 3c2670249af1-bi3qpnp77vpo CSeq: 7078 REGISTER Content-Length: 0 [7] 2010/12/21 17:38:48: SIP Rx tls:192.168.248.37:2518: INVITE sip:07957XXXXX@pbx.company.com;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-ixw3lkhd27j8;rport From: "Forty One" <sip:41@pbx.company.com>;tag=e37g31pan4 To: <sip:07957XXXXX@pbx.company.com;user=phone> Call-ID: 3c2bb1015719-v4rnefyq845q CSeq: 1 INVITE Max-Forwards: 70 Contact: <sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz>;reg-id=1 X-Serialnumber: 0004132612C1 P-Key-Flags: resolution="31x13", keys="4" User-Agent: snom370/8.4.18 Accept: application/sdp Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Supported: timer, 100rel, replaces, from-change Session-Expires: 3600;refresher=uas Min-SE: 90 Proxy-Require: buttons Content-Type: application/sdp Content-Length: 528 v=0 o=root 1996972669 1996972669 IN IP4 192.168.248.37 s=call c=IN IP4 192.168.248.37 t=0 0 m=audio 54568 RTP/AVP 9 0 8 2 3 18 4 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:i++e/E54J3oLoEbcEZSkWUM91rIS9ZpgQMxq4JiE a=rtpmap:9 g722/8000 a=rtpmap:0 pcmu/8000 a=rtpmap:8 pcma/8000 a=rtpmap:2 g726-32/8000 a=rtpmap:3 gsm/8000 a=rtpmap:18 g729/8000 a=fmtp:18 annexb=no a=rtpmap:4 g723/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-16 a=ptime:20 a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt a=sendrecv [7] 2010/12/21 17:38:48: SIP Tx tls:192.168.248.37:2518: SIP/2.0 100 Trying Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-ixw3lkhd27j8;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=e37g31pan4 To: <sip:07957XXXXX@pbx.company.com;user=phone>;tag=64bc6d70cc Call-ID: 3c2bb1015719-v4rnefyq845q CSeq: 1 INVITE Content-Length: 0 [7] 2010/12/21 17:38:48: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-932c4caafe78cd54327ae3bf5f5611dd;rport From: "Forty One" <sip:41@pbx.company.com>;tag=18970 To: "Forty One" <sip:41@pbx.company.com> Call-ID: j6xlabi4@pbx CSeq: 25789 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [7] 2010/12/21 17:38:48: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-0a541823ddb712b26370e71a423f96bc;rport From: "Forty One" <sip:41@pbx.company.com>;tag=60431 To: "Forty One" <sip:41@pbx.company.com> Call-ID: tvlggk5n@pbx CSeq: 9175 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [7] 2010/12/21 17:38:48: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-5c7cf7e355ba18246a3ee9dac985a5e8;rport From: "Forty One" <sip:41@pbx.company.com>;tag=65486 To: "Forty One" <sip:41@pbx.company.com> Call-ID: co5pt0jb@pbx CSeq: 49771 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 20 k=4 c=on x=ext [7] 2010/12/21 17:38:48: SIP Tx tls:192.168.248.37:2518: SIP/2.0 183 Session Progress Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-ixw3lkhd27j8;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=e37g31pan4 To: <sip:07957XXXXX@pbx.company.com;user=phone>;tag=64bc6d70cc Call-ID: 3c2bb1015719-v4rnefyq845q CSeq: 1 INVITE Contact: <sip:41@192.168.248.140:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 Require: 100rel RSeq: 1 Content-Type: application/sdp Content-Length: 429 v=0 o=- 10746 10746 IN IP4 192.168.248.140 s=- c=IN IP4 192.168.248.140 t=0 0 m=audio 60688 RTP/AVP 0 8 9 2 3 101 a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:eOhTOgXQXMvYRXPZsP3eunJH9KwMUaN1wwrcD/UB 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=ptime:20 a=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2010/12/21 17:38:48: SIP Tx udp:79.135.125.160:5082: INVITE sip:07957XXXXX@sip.gradwell.net;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-11eca58814c856594170e397b0171b88;rport From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=65117 To: <sip:07957XXXXX@sip.gradwell.net;user=phone> Call-ID: 6c50345d@pbx CSeq: 5067 INVITE Max-Forwards: 70 Contact: <sip:205XXXX@192.168.248.140:5060;transport=udp> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 P-Asserted-Identity: "Gradwell (Chris)" <sip:205XXXX@sip.gradwell.net> Content-Type: application/sdp Content-Length: 333 v=0 o=- 31917 31917 IN IP4 192.168.248.140 s=- c=IN IP4 192.168.248.140 t=0 0 m=audio 57040 RTP/AVP 0 8 9 2 3 101 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=rtcp-xr:rcvr-rtt=all voip-metrics a=sendrecv [7] 2010/12/21 17:38:48: SIP Rx udp:79.135.125.160:5082: SIP/2.0 403 Forbidden - no OBP Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-11eca58814c856594170e397b0171b88;rport=46788;received=188.220.16.125 From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=65117 To: <sip:07957XXXXX@sip.gradwell.net;user=phone>;tag=65c69fd7e8cf96760c930286580e648a.d0fd Call-ID: 6c50345d@pbx CSeq: 5067 INVITE Server: OpenSER (1.2.3-notls (i386/linux)) Content-Length: 0 [7] 2010/12/21 17:38:48: Call 6c50345d@pbx: Clear last INVITE [7] 2010/12/21 17:38:48: SIP Tx udp:79.135.125.160:5082: ACK sip:07957XXXXX@sip.gradwell.net;user=phone SIP/2.0 Via: SIP/2.0/UDP 192.168.248.140:5060;branch=z9hG4bK-11eca58814c856594170e397b0171b88;rport From: "Forty One" <sip:41@pbx.company.com;user=phone>;tag=65117 To: <sip:07957XXXXX@sip.gradwell.net;user=phone>;tag=65c69fd7e8cf96760c930286580e648a.d0fd Call-ID: 6c50345d@pbx CSeq: 5067 ACK Max-Forwards: 70 Contact: <sip:205XXXX@192.168.248.140:5060;transport=udp> P-Asserted-Identity: "Gradwell (Chris)" <sip:205XXXX@sip.gradwell.net> Content-Length: 0 [5] 2010/12/21 17:38:48: INVITE Response 403 Forbidden - no OBP: Terminate 6c50345d@pbx [7] 2010/12/21 17:38:48: SIP Tx tls:192.168.248.37:2518: SIP/2.0 403 Forbidden - no OBP Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-ixw3lkhd27j8;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=e37g31pan4 To: <sip:07957XXXXX@pbx.company.com;user=phone>;tag=64bc6d70cc Call-ID: 3c2bb1015719-v4rnefyq845q CSeq: 1 INVITE Contact: <sip:41@192.168.248.140:5061;transport=tls> Supported: 100rel, replaces, norefersub Allow-Events: refer Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Accept: application/sdp User-Agent: snom-PBX/4.2.0.3950 Content-Length: 0 [7] 2010/12/21 17:38:49: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-932c4caafe78cd54327ae3bf5f5611dd;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=18970 To: "Forty One" <sip:41@pbx.company.com> Call-ID: j6xlabi4@pbx CSeq: 25789 MESSAGE Content-Length: 0 [7] 2010/12/21 17:38:49: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-0a541823ddb712b26370e71a423f96bc;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=60431 To: "Forty One" <sip:41@pbx.company.com> Call-ID: tvlggk5n@pbx CSeq: 9175 MESSAGE Content-Length: 0 [7] 2010/12/21 17:38:49: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-5c7cf7e355ba18246a3ee9dac985a5e8;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=65486 To: "Forty One" <sip:41@pbx.company.com> Call-ID: co5pt0jb@pbx CSeq: 49771 MESSAGE Content-Length: 0 [7] 2010/12/21 17:38:49: SIP Rx tls:192.168.248.37:2518: PRACK sip:41@192.168.248.140:5061;transport=tls SIP/2.0 Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-pdc5p6ap6ogq;rport From: "Forty One" <sip:41@pbx.company.com>;tag=e37g31pan4 To: <sip:07957XXXXX@pbx.company.com;user=phone>;tag=64bc6d70cc Call-ID: 3c2bb1015719-v4rnefyq845q CSeq: 2 PRACK Max-Forwards: 70 Contact: <sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz>;reg-id=1 RAck: 1 1 INVITE Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE Allow-Events: talk, hold, refer, call-info Proxy-Require: buttons Content-Length: 0 [7] 2010/12/21 17:38:49: SIP Tx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-pdc5p6ap6ogq;rport=2518 From: "Forty One" <sip:41@pbx.company.com>;tag=e37g31pan4 To: <sip:07957XXXXX@pbx.company.com;user=phone>;tag=64bc6d70cc Call-ID: 3c2bb1015719-v4rnefyq845q CSeq: 2 PRACK Contact: <sip:41@192.168.248.140:5061;transport=tls> User-Agent: snom-PBX/4.2.0.3950 Content-Length: 0 [7] 2010/12/21 17:38:50: SIP Rx tls:192.168.248.37:2518: ACK sip:07957XXXXX@pbx.company.com;user=phone SIP/2.0 Via: SIP/2.0/TLS 192.168.248.37:2518;branch=z9hG4bK-ixw3lkhd27j8;rport From: "Forty One" <sip:41@pbx.company.com>;tag=e37g31pan4 To: <sip:07957XXXXX@pbx.company.com;user=phone>;tag=64bc6d70cc Call-ID: 3c2bb1015719-v4rnefyq845q CSeq: 1 ACK Max-Forwards: 70 Contact: <sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz>;reg-id=1 Proxy-Require: buttons Content-Length: 0 [7] 2010/12/21 17:38:50: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-847d23b4c2aa9196e2da7f8e58fca4c5;rport From: "Forty One" <sip:41@pbx.company.com>;tag=7386 To: "Forty One" <sip:41@pbx.company.com> Call-ID: n7sxdflw@pbx CSeq: 19559 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [7] 2010/12/21 17:38:50: SIP Tx tls:192.168.248.37:2518: MESSAGE sip:41@192.168.248.37:2518;transport=tls;line=w6t9bmkz SIP/2.0 Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-70b87a01334f3db3a708646baaf82f48;rport From: "Forty One" <sip:41@pbx.company.com>;tag=57740 To: "Forty One" <sip:41@pbx.company.com> Call-ID: ylcx7b5q@pbx CSeq: 29476 MESSAGE Max-Forwards: 70 Contact: <sip:192.168.248.140:5061;transport=tls> Subject: buttons Content-Type: application/x-buttons Content-Length: 14 k=4 x=ext [6] 2010/12/21 17:38:50: SIP TCP/TLS timeout on 192.168.248.38:3617, closing connection [7] 2010/12/21 17:38:50: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-847d23b4c2aa9196e2da7f8e58fca4c5;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=7386 To: "Forty One" <sip:41@pbx.company.com> Call-ID: n7sxdflw@pbx CSeq: 19559 MESSAGE Content-Length: 0 [7] 2010/12/21 17:38:50: SIP Rx tls:192.168.248.37:2518: SIP/2.0 200 Ok Via: SIP/2.0/TLS 192.168.248.140:5061;branch=z9hG4bK-70b87a01334f3db3a708646baaf82f48;rport=5061 From: "Forty One" <sip:41@pbx.company.com>;tag=57740 To: "Forty One" <sip:41@pbx.company.com> Call-ID: ylcx7b5q@pbx CSeq: 29476 MESSAGE Content-Length: 0 Quote Link to comment Share on other sites More sharing options...
mattlandis Posted December 21, 2010 Report Share Posted December 21, 2010 If you use Nexvortex SIP trunk I can give you an exact configuration that works. I really think that SIP trunk providers should email an standard XML file to client that SIP PBX's can import to take away this fiddly stuff... Matt Quote Link to comment Share on other sites More sharing options...
Vodia PBX Posted December 22, 2010 Report Share Posted December 22, 2010 Privacy: pai Seems like sipgate does not support P-Asserted-Identity (RFC3325). Choose another mode, probably Remote-Party-ID or "No hide". With Gradwell:- Gradwell probably has the same problem. It is shocking how difficult for providers it is to understand the meaning of the From-header, especially for redirected calls. Quote Link to comment Share on other sites More sharing options...
Telis Ltd Posted March 10, 2011 Author Report Share Posted March 10, 2011 Sorry, I forgot about this thread! @Matt Thanks for the offer of help, but I'm after a UK based provider. An industry standard XML file would be a good way of getting better interop. @pbxnsip I switched to a SIP trunk from gradwell and got it working that way. I will try a SIP registration account with Remote-Party-ID or "No hide" and see if it works and post back out of interest however. Quote Link to comment Share on other sites More sharing options...
Irksome Posted April 13, 2011 Report Share Posted April 13, 2011 Setting the Remote Party to No Indication worked for my Sipgate trunk. Irksome 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.