FreePBX | Register | Issues | Wiki | Portal | Support

SIP Trunk not connecting to server

siptrunk
freepbx
Tags: #<Tag:0x00007f74a77b64c0> #<Tag:0x00007f74a77b5f98>

(Dirkus) #1

I have a FreePBX PBXact server that stopped working yesterday. It was after an reload of FreePBX and an exterrnal IP address change.

I have captured a request packet from my FreePBX server to my provider. I get a “SIP/2.0 403 Forbidden” as my return. I also have captured packet from a 3CX softphone request that does connect and work. The biggest difference that I see is that the softphone uses a Method type of REQUEST and the FreePBX sends a Method type of OPTION .

Here is the successful softphone request.

No. Time Source Destination Protocol Length Info
3 0.067277 208.73.146.93 196.53.97.42 SIP 531 Status: 200 OK (1 binding) |

Frame 3: 531 bytes on wire (4248 bits), 531 bytes captured (4248 bits)
Linux cooked capture
Packet type: Unicast to us (0)
Link-layer address type: 1
Link-layer address length: 6
Source: Routerbo_eb:c8:ce (64:d1:54:eb:c8:ce)
Unused: 0000
Protocol: IPv4 (0x0800)
Internet Protocol Version 4, Src: 208.73.146.93, Dst: 196.53.97.42
User Datagram Protocol, Src Port: 5060, Dst Port: 64712
Source Port: 5060
Destination Port: 64712
Length: 495
Checksum: 0xca33 [unverified]
[Checksum Status: Unverified]
[Stream index: 1]
Session Initiation Protocol (200)
Status-Line: SIP/2.0 200 OK
Status-Code: 200
[Resent Packet: False]
[Request Frame: 2]
[Response Time (ms): 67]
Message Header
Via: SIP/2.0/UDP 192.168.68.200:64712;received=196.53.97.42;branch=z9hG4bK-d8754z-1a01e723ea615e0a-1—d8754z-;rport=64712
Transport: UDP
Sent-by Address: 192.168.68.200
Sent-by port: 64712
Received: 196.53.97.42
Branch: z9hG4bK-d8754z-1a01e723ea615e0a-1—d8754z-
RPort: 64712
To: "435-755-0863"sip:699285138@trunking.voipdnsservers.com:5060;tag=aprqes9r96l5g2ig5-rqj87c10000i0
SIP Display info: “435-755-0863”
SIP to address: sip:699285138@trunking.voipdnsservers.com:5060
SIP to tag: aprqes9r96l5g2ig5-rqj87c10000i0
From: "435-755-0863"sip:699285138@trunking.voipdnsservers.com:5060;tag=84750847
SIP Display info: “435-755-0863”
SIP from address: sip:699285138@trunking.voipdnsservers.com:5060
SIP from tag: 84750847
Call-ID: MzBhMTdiMDdlOGNjZmU2OGEyODA0NGNmNTEyYTJmNWY.
CSeq: 9 REGISTER
Sequence Number: 9
Method: REGISTER
Contact: sip:699285138@192.168.68.200:64712;rinstance=731af31fe94b8a33;expires=30
Contact URI: sip:699285138@192.168.68.200:64712;rinstance=731af31fe94b8a33
Contact parameter: expires=30


Here is the packet of the failing FreePBX.

No. Time Source Destination Protocol Length Info
1 0.000000 196.53.97.43 208.73.146.93 SIP 529 Request: OPTIONS sip:699285138@trunking.voipdnsservers.com:5060 |

Frame 1: 529 bytes on wire (4232 bits), 529 bytes captured (4232 bits)
Ethernet II, Src: Intel_ef:15:21 (00:90:27:ef:15:21), Dst: Routerbo_eb:c8:ce (64:d1:54:eb:c8:ce)
Internet Protocol Version 4, Src: 196.53.97.43, Dst: 208.73.146.93
User Datagram Protocol, Src Port: 5060, Dst Port: 5060
Source Port: 5060
Destination Port: 5060
Length: 495
Checksum: 0x8a08 [unverified]
[Checksum Status: Unverified]
[Stream index: 0]
Session Initiation Protocol (OPTIONS)
Request-Line: OPTIONS sip:699285138@trunking.voipdnsservers.com:5060 SIP/2.0
Method: OPTIONS
Request-URI: sip:699285138@trunking.voipdnsservers.com:5060
Request-URI User Part: 699285138
Request-URI Host Part: trunking.voipdnsservers.com
Request-URI Host Port: 5060
[Resent Packet: False]
Message Header
Via: SIP/2.0/UDP 196.53.97.43:5060;rport;branch=z9hG4bKPjf8f79362-8759-42a1-bb39-a05933c162f4
Transport: UDP
Sent-by Address: 196.53.97.43
Sent-by port: 5060
RPort: rport
Branch: z9hG4bKPjf8f79362-8759-42a1-bb39-a05933c162f4
From: sip:699285138@trunking.voipdnsservers.com;tag=4480b617-09ab-4b43-a844-ec8b01979e50
SIP from address: sip:699285138@trunking.voipdnsservers.com
SIP from tag: 4480b617-09ab-4b43-a844-ec8b01979e50
To: sip:699285138@trunking.voipdnsservers.com
SIP to address: sip:699285138@trunking.voipdnsservers.com
Contact: sip:699285138@196.53.97.43:5060
Contact URI: sip:699285138@196.53.97.43:5060
Call-ID: 7462035c-8178-43ff-97e5-58c7adb5318f
CSeq: 3397 OPTIONS
Sequence Number: 3397
Method: OPTIONS
Max-Forwards: 70
User-Agent: FPBX-13.0.197(13.23.1)
Content-Length: 0


Any thoughts? I can provide more data on request.

Dirkus


(Tom Ray) #2

A REGISTER and an OPTIONS are not the same. If you’re getting a 403 Forbidden back on a REGISTER it generally means there is an auth issue like a bad password.


(Dirkus) #3

I’m not sure what is broken (borken) in my FreePBX configuration that is causing an OPTIONS request instead of a REGISTER request.

What should I be looking for?


(system) closed #4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.