onestopit Posted September 16, 2009 Report Share Posted September 16, 2009 We're trying to configure a Gradwell Enterprise SIP Trunk with PBXnSIP and getting '403 Method not supported' - which we also get on a standard X-lite client when we've tried it. I've been told by Gradwell support that this service doesn't require a username/password and authenticates by permitted IP address. How do I configure PBXnSIP Trunks to support this configuration? Quote Link to comment Share on other sites More sharing options...
onestopit Posted September 16, 2009 Author Report Share Posted September 16, 2009 ... I should also add we've tried leaving the username and password blank in the Trunk config pages! Quote Link to comment Share on other sites More sharing options...
pbx support Posted September 17, 2009 Report Share Posted September 17, 2009 We're trying to configure a Gradwell Enterprise SIP Trunk with PBXnSIP and getting '403 Method not supported' - which we also get on a standard X-lite client when we've tried it. I've been told by Gradwell support that this service doesn't require a username/password and authenticates by permitted IP address. How do I configure PBXnSIP Trunks to support this configuration? You should set the trunk type as "SIP Gateway". This does not need username / password. Just set the IP address/name under the domain and the outbound proxy field. Quote Link to comment Share on other sites More sharing options...
onestopit Posted September 17, 2009 Author Report Share Posted September 17, 2009 Ok... doing this and setting up dialplan to suit I now get... [5] 2009/09/17 12:34:59: Last message repeated 2 times [8] 2009/09/17 12:34:59: Could not find a trunk (1 trunks) [5] 2009/09/17 12:48:15: Trunk 6 (Gradwell_EST) has outbound proxy udp:212.11.94.100:5060 [8] 2009/09/17 12:48:22: Could not find a trunk (1 trunks) [5] 2009/09/17 12:49:06: Trunk 6 (Gradwell_EST) has outbound proxy udp:212.11.94.100:5060 Quote Link to comment Share on other sites More sharing options...
onestopit Posted September 17, 2009 Author Report Share Posted September 17, 2009 I’ve tried setting it up as a SIP Gateway as suggested by someone on your Forum site, and it seems to be on the right direction, but I’m not getting out. I’m using X-Lite as my extension and getting “Call Failed: Access denied to SIP Trunk Out. In the PBX Logs, the same call produces... [8] 2009/09/17 13:09:38: Last message repeated 6 times [9] 2009/09/17 13:09:38: SIP Rx udp:10.10.10.18:40152: REGISTER sip:pbx.onestopit.com SIP/2.0 Via: SIP/2.0/UDP 10.10.10.18:40152;branch=z9hG4bK-d8754z-c0283e0af73b2e48-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:101@10.10.10.18:40152;rinstance=19e381e125a7982b> To: "101"<sip:101@pbx.onestopit.com> From: "101"<sip:101@pbx.onestopit.com>;tag=327d3242 Call-ID: NjUyZDQzYzU1NjhkMDA1YTZkMTM4ODUzYjc2YTZhNTQ. CSeq: 86 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite release 1103k stamp 53621 Authorization: Digest username="101",realm="pbx.onestopit.com",nonce="a8062d0f2ebedc74c86e2189a3a203ea",uri="sip:pbx.onestopit.com",response="eacb5655bec1fdb7c3d297b3d97507fa",algorithm=MD5 Content-Length: 0 [9] 2009/09/17 13:09:38: Resolve 14255: aaaa udp 10.10.10.18 40152 [9] 2009/09/17 13:09:38: Resolve 14255: a udp 10.10.10.18 40152 [9] 2009/09/17 13:09:38: Resolve 14255: udp 10.10.10.18 40152 [9] 2009/09/17 13:09:38: SIP Tx udp:10.10.10.18:40152: SIP/2.0 200 Ok Via: SIP/2.0/UDP 10.10.10.18:40152;branch=z9hG4bK-d8754z-c0283e0af73b2e48-1---d8754z-;rport=40152 From: "101" <sip:101@pbx.onestopit.com>;tag=327d3242 To: "101" <sip:101@pbx.onestopit.com>;tag=fc8f3ea84b Call-ID: NjUyZDQzYzU1NjhkMDA1YTZkMTM4ODUzYjc2YTZhNTQ. CSeq: 86 REGISTER Contact: <sip:101@10.10.10.18:40152;rinstance=19e381e125a7982b>;expires=28 Content-Length: 0 [8] 2009/09/17 13:10:00: Could not find a trunk (1 trunks) [9] 2009/09/17 13:10:00: Resolve 14256: aaaa udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14256: a udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14256: udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14257: aaaa udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14257: a udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14257: udp 10.10.10.18 40152 [8] 2009/09/17 13:10:00: Tagging request with existing tag [9] 2009/09/17 13:10:00: Resolve 14258: aaaa udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14258: a udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14258: udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14259: url sip:sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14259: naptr sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14260: aaaa udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14260: a udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14260: udp 10.10.10.18 40152 [8] 2009/09/17 13:10:00: DNS: Add dns_naptr sip.trunk.gradwell.com (ttl=60) [9] 2009/09/17 13:10:00: Resolve 14259: naptr sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14259: srv tls _sips._tcp.sip.trunk.gradwell.com [8] 2009/09/17 13:10:00: DNS: Add dns_srv _sips._tcp.sip.trunk.gradwell.com (ttl=60) [9] 2009/09/17 13:10:00: Resolve 14259: srv tls _sips._tcp.sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14259: srv tcp _sip._tcp.sip.trunk.gradwell.com [8] 2009/09/17 13:10:00: DNS: Add dns_srv _sip._tcp.sip.trunk.gradwell.com (ttl=60) [9] 2009/09/17 13:10:00: Resolve 14259: srv tcp _sip._tcp.sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14259: srv udp _sip._udp.sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14259: a udp v-sip-trunk-out-f1.gradwell.net 5060 [9] 2009/09/17 13:10:00: Resolve 14259: udp 212.11.94.100 5060 [7] 2009/09/17 13:10:00: Call ba30980f@pbx#55282: Clear last INVITE [9] 2009/09/17 13:10:00: Resolve 14261: url sip:sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14261: naptr sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14261: srv tls _sips._tcp.sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14261: srv tcp _sip._tcp.sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14261: srv udp _sip._udp.sip.trunk.gradwell.com [9] 2009/09/17 13:10:00: Resolve 14261: a udp v-sip-trunk-out-f1.gradwell.net 5060 [9] 2009/09/17 13:10:00: Resolve 14261: udp 212.11.94.100 5060 [5] 2009/09/17 13:10:00: INVITE Response 403 Access denied to SIP Trunk Out: Terminate ba30980f@pbx [7] 2009/09/17 13:10:00: Other Ports: 1 [7] 2009/09/17 13:10:00: Call Port: YjI5MjQyMDk4MDI3YWY5NjA0N2FkZjk4OTNlOGQzNzU.#87038acc4b [9] 2009/09/17 13:10:00: Resolve 14262: aaaa udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14262: a udp 10.10.10.18 40152 [9] 2009/09/17 13:10:00: Resolve 14262: udp 10.10.10.18 40152 [9] 2009/09/17 13:10:01: SIP Rx udp:10.10.10.18:40152: REGISTER sip:pbx.onestopit.com SIP/2.0 Via: SIP/2.0/UDP 10.10.10.18:40152;branch=z9hG4bK-d8754z-d0513f0bac781c7c-1---d8754z-;rport Max-Forwards: 70 Contact: <sip:101@10.10.10.18:40152;rinstance=19e381e125a7982b> To: "101"<sip:101@pbx.onestopit.com> From: "101"<sip:101@pbx.onestopit.com>;tag=327d3242 Call-ID: NjUyZDQzYzU1NjhkMDA1YTZkMTM4ODUzYjc2YTZhNTQ. CSeq: 87 REGISTER Expires: 3600 Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO User-Agent: X-Lite release 1103k stamp 53621 Authorization: Digest username="101",realm="pbx.onestopit.com",nonce="a8062d0f2ebedc74c86e2189a3a203ea",uri="sip:pbx.onestopit.com",response="eacb5655bec1fdb7c3d297b3d97507fa",algorithm=MD5 Content-Length: 0 [9] 2009/09/17 13:10:01: Resolve 14263: aaaa udp 10.10.10.18 40152 [9] 2009/09/17 13:10:01: Resolve 14263: a udp 10.10.10.18 40152 [9] 2009/09/17 13:10:01: Resolve 14263: udp 10.10.10.18 40152 [9] 2009/09/17 13:10:01: SIP Tx udp:10.10.10.18:40152: SIP/2.0 200 Ok Via: SIP/2.0/UDP 10.10.10.18:40152;branch=z9hG4bK-d8754z-d0513f0bac781c7c-1---d8754z-;rport=40152 From: "101" <sip:101@pbx.onestopit.com>;tag=327d3242 To: "101" <sip:101@pbx.onestopit.com>;tag=fc8f3ea84b Call-ID: NjUyZDQzYzU1NjhkMDA1YTZkMTM4ODUzYjc2YTZhNTQ. CSeq: 87 REGISTER Contact: <sip:101@10.10.10.18:40152;rinstance=19e381e125a7982b>;expires=29 Content-Length: 0 Any ideas? Our trunk provider says they only authenticate by IP (no username or password) and CLI? Quote Link to comment Share on other sites More sharing options...
pbx support Posted September 18, 2009 Report Share Posted September 18, 2009 Are are almost there on getting the the log. Please follow https://pbxnsipsupport.com/index.php?_m=kno...;kbarticleid=58 to setup the log properly. Once you do that, place a call using x-lite and post the log. I’ve tried setting it up as a SIP Gateway as suggested by someone on your Forum site, and it seems to be on the right direction, but I’m not getting out. I’m using X-Lite as my extension and getting “Call Failed: Access denied to SIP Trunk Out. In the PBX Logs, the same call produces...Any ideas? . . . Our trunk provider says they only authenticate by IP (no username or password) and CLI? Quote Link to comment Share on other sites More sharing options...
onestopit Posted September 18, 2009 Author Report Share Posted September 18, 2009 Sorted... just needed to change to a SIP Gateway and enter our outgoing CLI in the ANI field. 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.