Implementing a new installation,
All calls are sent over a single trunk to a session border controller.
One of the outbound routes I have configured for 4 digit numbers so its basically an intra company route with XXXX as the dial pattern.
This seems to work just fine with numbers starting with 0, IE 0120.
Via: SIP/2.0/UDP 10.0.2.29:5060;rport;branch=z9hG4bKPj9a043361-6cc0-41c4-8c40-7c42164e87b5
From: "Brandon Desk Phone" <sip:[email protected]>;tag=6cef121a-bfc2-44d0-90bf-12bef96b4adc
To: <sip:[email protected]>
Contact: <sip:[email protected]:5060>
Call-ID: 194d29ac-d56e-4cbb-8d5e-e0f42997928a
CSeq: 23868 INVITE
Allow: OPTIONS, INVITE, ACK, BYE, CANCEL, UPDATE, PRACK, REGISTER, SUBSCRIBE, NOTIFY, PUBLISH, MESSAGE, REFER
Supported: 100rel, timer, replaces, norefersub, histinfo
Session-Expires: 1800
Min-SE: 90
Max-Forwards: 70
User-Agent: FPBX-16.0.40(18.13.0)
Content-Type: application/sdp
Content-Length: 331
v=0
o=- 992086666 992086666 IN IP4 10.0.2.29
s=Asterisk
c=IN IP4 10.0.2.29
t=0 0
m=audio 10344 RTP/AVP 0 8 3 111 9 101
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:111 G726-32/8000
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=maxptime:150
a=sendrecv
The to and contact is correct. 10.0.2.131 is the SBC
However we have another system that is configured to work with the SBC that is reachable through extension 7777
FreePBX is not routing that call out the trunk to the SBC. It is trying to contact 7777@itself. There is no extension 7777 registered on FreePBX so it comes back and says the number is unavailable or something like that. I even tried to specifically denote 7777 in the route dial
plan
I can only attach one pic so here is the pasted invite from asterisk logs where FreePBX is sending invite to itself.
<--- Received SIP request (1168 bytes) from UDP:10.0.240.112:5060 --->
INVITE sip:[email protected]:5060 SIP/2.0
Via: SIP/2.0/UDP 10.0.240.112:5060;branch=z9hG4bK470873887
From: "7500-Brandon Desk Phone" <sip:[email protected]:5060>;tag=1490387275
To: <sip:[email protected]:5060>
Call-ID: [email protected]
CSeq: 2 INVITE
Contact: <sip:[email protected]:5060>
Authorization: Digest username="7500", realm="asterisk", nonce="1683552012/2e90c a41411a67234a7b0ea5eae277a0", uri="sip:[email protected]:5060", response="24e55666 6ed2ffbd4d0b1fd9e8af0453", algorithm=MD5, cnonce="470969572", opaque="1500d2254c 54707b", qop=auth, nc=00000001
Content-Type: application/sdp
Allow: INVITE, INFO, PRACK, ACK, BYE, CANCEL, OPTIONS, NOTIFY, REGISTER, SUBSCRI BE, REFER, PUBLISH, UPDATE, MESSAGE
Max-Forwards: 70
User-Agent: Yealink SIP-T23G 44.84.200.7
Allow-Events: talk,hold,conference,refer,check-sync
Supported: replaces
Content-Length: 292
So my question is, why if I have an Outbound route configured to catch all 4 digit numbers and send them to the SBC is it only working on certain 4 digit numbers and is there a way to work around it if it by design.
Ignore the fact that it is calling 10.0.240.2 I just have the phone registered to a separate NIC on the FreePBX server. 10.0.2.29 and 10.0.240.2 are the same machines and the result was still the same.
