lieveluc Posted November 2, 2009 Report Posted November 2, 2009 I tried to setup a PSTN Trunk for a SwyxConnect 1722 (which is identical to Lancom 1722). Although i tried several settings, i was not able to register the Trunk. I checked with the embedded Trace functionality of the SwyxConnect the SIP packets and noticed that Pbxnsip returned 404 not found. Following you find configuration information and the trace - any idea what is wrong? Pbxsnip does have the ip address 15.137.40.40 and the SwyxConnect 1722 15.137.40.2. The trunk settings in pbxnsip are: Type : SIP Gateway Direction : Inbound and Outbound Account : pbxnsip Domain: 15.137.40.40 Username: pbxnsip Password : test Outbound Proxy : 15.137.40.2 The trunk settings in swyxconnect are: Mode : Gateway Provider Name : PBXNSIP SIP domain/realm : 15.137.40.40 Registrar : 15.137.40.40 Outbound Proxy : 15.137.40.40 Port : 5060 SIP-ID/user : pbxnsip Password : test Here you see a part of the trace file: [sIP-Packet] 2009/11/01 23:00:10,140 Sending datagram with length 461 from 15.137.40.2:33657 to 15.137.40.40:5060 REGISTER sip:15.137.40.40 SIP/2.0 Via: SIP/2.0/UDP 15.137.40.2:33657;branch=z9hG4bK-604644e1-8d0015f1 From: <sip:pbxnsip@15.137.40.40>;tag=-718667857-198420311 To: <sip:pbxnsip@15.137.40.40> Call-ID: pbxnsip-15.137.40.40-f979c6c9@00a05711ad02 CSeq: 4 REGISTER Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS Max-Forwards: 70 Contact: * Expires: 0 User-Agent: SwyxConnect 1722 (Annex / 7.33.0002 / 30.04.2008 Content-Length: 0 [sIP-Packet] 2009/11/01 23:00:10,140 Receiving datagram with length 283 from 15.137.40.40:5060 to 15.137.40.2:33657 SIP/2.0 200 Ok Via: SIP/2.0/UDP 15.137.40.2:33657;branch=z9hG4bK-604644e1-8d0015f1 From: <sip:pbxnsip@15.137.40.40>;tag=-718667857-198420311 To: <sip:pbxnsip@15.137.40.40>;tag=96d83a6fc9 Call-ID: pbxnsip-15.137.40.40-f979c6c9@00a05711ad02 CSeq: 4 REGISTER Content-Length: 0 [sIP-Packet] 2009/11/01 23:00:10,150 Sending datagram with length 328 from 15.137.40.2:38324 to 15.137.40.40:5060 OPTIONS sip:15.137.40.40 SIP/2.0 Via: SIP/2.0/UDP 15.137.40.2:38324;branch=z9hG4bK-fb11f43c-6333fc89 From: <sip:15.137.40.40>;tag=1428758557--653587235 To: <sip:15.137.40.40> Call-ID: 3813582362@00a05711ad02 CSeq: 1 OPTIONS Max-Forwards: 70 Accept: application/sdp Contact: <sip:15.137.40.2:38324> Content-Length: 0 [sIP-Packet] 2009/11/01 23:00:10,150 Receiving datagram with length 309 from 15.137.40.40:5060 to 15.137.40.2:38324 SIP/2.0 200 Ok Via: SIP/2.0/UDP 15.137.40.2:38324;branch=z9hG4bK-fb11f43c-6333fc89 From: <sip:15.137.40.40>;tag=1428758557--653587235 To: <sip:15.137.40.40>;tag=921d71ddaf Call-ID: 3813582362@00a05711ad02 CSeq: 1 OPTIONS Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE Content-Length: 0 [sIP-Packet] 2009/11/01 23:00:12,150 Sending datagram with length 494 from 15.137.40.2:33657 to 15.137.40.40:5060 REGISTER sip:15.137.40.40 SIP/2.0 Via: SIP/2.0/UDP 15.137.40.2:33657;branch=z9hG4bK-d0dfe795-17c81901 From: <sip:pbxnsip@15.137.40.40>;tag=-1077970787-1735904640 To: <sip:pbxnsip@15.137.40.40> Call-ID: pbxnsip-15.137.40.40-f979c6c9@00a05711ad02 CSeq: 5 REGISTER Allow: REGISTER, INVITE, ACK, CANCEL, BYE, REFER, NOTIFY, OPTIONS Max-Forwards: 70 Contact: <sip:pbxnsip@15.137.40.2:33657> Expires: 60 User-Agent: SwyxConnect 1722 (Annex / 7.33.0002 / 30.04.2008 Content-Length: 0 [sIP-Packet] 2009/11/01 23:00:12,150 Receiving datagram with length 292 from 15.137.40.40:5060 to 15.137.40.2:33657 SIP/2.0 404 Not Found Via: SIP/2.0/UDP 15.137.40.2:33657;branch=z9hG4bK-d0dfe795-17c81901 From: <sip:pbxnsip@15.137.40.40>;tag=-1077970787-1735904640 To: <sip:pbxnsip@15.137.40.40>;tag=96d83a6fc9 Call-ID: pbxnsip-15.137.40.40-f979c6c9@00a05711ad02 CSeq: 5 REGISTER Content-Length: 0 Quote
pbx support Posted November 2, 2009 Report Posted November 2, 2009 Couple of things - 1. You do not need to register a "SIP Gateway trunk". Only "SIP Registration" trunks need to be registered. If you want the trunk to be registered, change the trunk type to be "SIP Registration". 2. For the trunk settings on the PBX, the "domain" and the "outbound proxy" have to be same (unless the SwyxConnect server instructs you otherwise) Most of the information about the trunks is in http://kiwi.pbxnsip.com/index.php/Trunk_Settings (I could not find the pbxnsipsupport site page for this ) I tried to setup a PSTN Trunk for a SwyxConnect 1722 (which is identical to Lancom 1722). Although i tried several settings, i was not able to register the Trunk. I checked with the embedded Trace functionality of the SwyxConnect the SIP packets and noticed that Pbxnsip returned 404 not found. Following you find configuration information and the trace - any idea what is wrong? Pbxsnip does have the ip address 15.137.40.40 and the SwyxConnect 1722 15.137.40.2. The trunk settings in pbxnsip are: Type : SIP Gateway Direction : Inbound and Outbound Account : pbxnsip Domain: 15.137.40.40 Username: pbxnsip Password : test Outbound Proxy : 15.137.40.2 The trunk settings in swyxconnect are: Mode : Gateway Provider Name : PBXNSIP SIP domain/realm : 15.137.40.40 Registrar : 15.137.40.40 Outbound Proxy : 15.137.40.40 Port : 5060 SIP-ID/user : pbxnsip Password : test Content-Length: 0 Quote
Vodia PBX Posted November 3, 2009 Report Posted November 3, 2009 Couple of things - 1. You do not need to register a "SIP Gateway trunk". Only "SIP Registration" trunks need to be registered. If you want the trunk to be registered, change the trunk type to be "SIP Registration". 2. For the trunk settings on the PBX, the "domain" and the "outbound proxy" have to be same (unless the SwyxConnect server instructs you otherwise) You cannot register a trunk to the PBX (you can register a trunk from the PBX to an external registrar). You can register only a extension. Now sure if that makes sense here; but this is worth a try. Otherwise, I would just use the gateway mode of the trunk and use the outbound proxy on the gateway. Quote
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.