Jump to content

lieveluc

Members
  • Posts

    13
  • Joined

  • Last visited

lieveluc's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. We do have a requirement to combine Pbxnsip with an ISDN BRI PSTN Gateway. Any recommendations? What about Patton Smartnode 4554? Thanks for helping out
  2. Thanks for the tips - i was able to get it working. The Lancom device runs smoothly with Pbxnsip
  3. 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
  4. I added as outbound proxy 15.137.40.2 but it still does not work.
  5. thanks for the input - i did delete the entry in the authorization name of the iSoftPhone and now it works
  6. yes , i also tried SIP without TLS. According the SIP log from the iSoftPhone Authentication is required. Message sent: (to dest=15.137.40.40:5060) REGISTER sip:15.137.40.40 SIP/2.0 Via: SIP/2.0/UDP 15.137.40.20:5060;rport;branch=z9hG4bK2121148679 From: <sip:55@15.137.40.40>;tag=1980515830 To: <sip:55@15.137.40.40> Call-ID: 2048568031 CSeq: 1 REGISTER Contact: <sip:55@15.137.40.20:5060;line=6ea58eb8426814e> Max-Forwards: 70 User-Agent: iSoftPhone 2.6060 Expires: 1800 Supported: 100rel Supported: path Content-Length: 0 Received message: SIP/2.0 401 Authentication Required Via: SIP/2.0/UDP 15.137.40.20:5060;rport=5060;branch=z9hG4bK2121148679 From: <sip:55@15.137.40.40>;tag=1980515830 To: <sip:55@15.137.40.40>;tag=9115ce87a5 Call-ID: 2048568031 CSeq: 1 REGISTER User-Agent: pbxnsip-PBX/3.4.0.3201 WWW-Authenticate: Digest realm="15.137.40.40",nonce="032e18d1169b67c4854bf26aefcf1714",domain="sip:15.137.40.40",algorithm=MD5 Content-Length: 0
  7. Hi i need some help here regarding the configuration of the Trunk within pbxnsip and for the SIP Gateway. In my network pbxnsip does have the ip address 15.137.40.40 and the lancom 1722 Gateway 15.137.40.2 How should i configure the Trunk within pbxnsip? I used following settings without success: Name: test Type: SIP Gateway Direction: Inbound and outbound Domain: 15.137.40.2 Username: pbxnsip Password: test All other parameters are default. Did i forget something? Thanks for your support
  8. Hi changing the port number to 5060 did not work.
  9. i changed the configuration as you described, however the iSoftPhone is not possible to register. After i checked the SIP log from the iSoftPhone it seems that it is a problm with the certificate. See following log information: eXosip: Couldn't read CA list New binding with 15.137.40.40 eXosip: Couldn't read CA list Failed to verify remote certificate Message sent: REGISTER sip:15.137.40.40 SIP/2.0 Via: SIP/2.0/TLS 15.137.40.20:5061;rport;branch=z9hG4bK1009892605 From: <sip:55@15.137.40.40>;tag=1555775356 To: <sip:55@15.137.40.40> Call-ID: 575753453 CSeq: 1 REGISTER Contact: <sip:55@15.137.40.20:5061;transport=TLS;line=1cd5977bcaeb059> Max-Forwards: 70 User-Agent: iSoftPhone 2.6060 Expires: 1800 Supported: 100rel Supported: path Content-Length: 0 (to dest=15.137.40.40:5061) cb_transport_error (id=1) cb_nict_kill_transaction (id=1) Any idea what to do next?
  10. I just installed pbxnsip and it is up and running with Snom Phones. I did load the default template Office which is provided on the pbxnsip webpage (domain name = localhost). However i do have a problem when using the iSoftphone from Call4Mac.com. I can`t register the iSoftphone to pbxnsip. I do use following settings: Server address = ip address of pbxnsip User name = 42 Password = as defined in the profile for the extension 42 Authorization Name = localhost@ip address of pbxnsip Local SIP port = 5061 SIP Proxy = ip address of pbxnsip Protocol = SIP-TLS Any idea what is wrong?
  11. I just installed the pbxnsip software on a snow leopard server. On this server already a web server is installed on port 80. Now i can`t access the web page of pbxnsip. Where can i change the default port number for the pbnxsip web server? It would be helpful to change the default port number for the web server during the installation.
  12. Does any one has experience with using a Lancom 1722 as SIP Gateway for Pbxnsip? If yes, please provide instructions Thanks
×
×
  • Create New...