Twilio SIP inbound trunk issue with MBG

[bryanb]

We just setup a new Twilio trunk. I have outbound calls functioning properly but inbound calls are failing.

this is the message is see in my tug log

2017-07-11 10:34:38.918 {140343923427072} [UA] CSeq: 1 INVITE
2017-07-11 10:34:38.918 {140343923427072} [UA] User-Agent: Mitel Border GW/4.8.0.19-01
2017-07-11 10:34:38.918 {140343923427072} [UA] Content-Length: 0
2017-07-11 10:34:38.918 {140343923427072} [UA]
2017-07-11 10:34:38.918 {140343923427072} [UA]
2017-07-11 10:34:38.918 {140343924410112} [UA] Rejecting client '+44XXXXXXXXXX', no entry found in clients db with auth enabled!
2017-07-11 10:34:38.918 2017-07-11 10:34:38.918 TUGSEC::tugid:mas.mycompany.local_1,sip user:+44XXXXXXXXXX,event:invalid user,possible scan from ip:54.171.127.192:5060

[ralph]

It would appear to me that the carrier is rejecting you because it doesn't recognize you as an authorized caller.
Are you sure you caller ID is correct?

Ralph

[acejavelin]

It would appear to me that the carrier is rejecting you because it doesn't recognize you as an authorized caller.
Are you sure you caller ID is correct?

Ralph

I think the OP was talking about inbound calls, those logs are the Mitel or MBG rejecting the call...

I reviewed them but have no idea what the issue is.

[sarond]

Do you have your DID programmed correctly?
Can you do a pcap trace on port 5060 (MBG>Administration>Diagnostics>Run  packet trace with filter option "port 5060")
Start the capture, make the call, stop the capture and open file with wireshark.

[bryanb]

Attached is the packet capture

[acejavelin]

Attached is the packet capture

Do you have your DID programmed as 442038268079? The full number?

[sarond]

Have you got inbound authentication disabled in the SIP Peer?

[bryanb]

@acejavelin - I had a vendor configure this for me(I'm not very happy with them a this point). Could you please guide me in the correct direction to configure/check this configuration.

@sarond - I do not have authentication configured. I reviewed the Mitel/Twilio document and it says that it is not supported.


I have also attached the Mitel/Twilio configuration document.

[sarond]

Confirm that your number exists in the "SIP Peer Profile Assignment by Incoming DID" form as instructed on page 12.

[bryanb]

In my configuration I have listed 4* for the incoming sip DID range.

[acejavelin]

Might not be the issue, but check your Trunk Attributes form and the one that is assigned to this peer group, and look at "Dial-In Trunks Incoming Digit Modification - Absorb", verify it is "0" and not blank... this field cannot be blank but is a common mistake even with experienced technicians.

Dial-In Trunks Incoming Digit Modification - Absorb

Number of leading digits to remove from the digit stream received from the Central Office or remote system. The maximum number of digits is 26. Dial-in trunks used as incoming trunks must always have an entry in the Absorb column. (You must enter "0" if no digits are to be absorbed. If you leave this field as Blank, calls will fail).

Default Value: <blank>

[bryanb]

I have confirmed that the Absorb is sent to 0. Do you think my issue could be that when twilio is sending me the number in the trunk it has a "+" in front of it and in my DID is just 4*?

[dilkie]

that looks to me to be a case of MBG not recognizing that the packet came from the trunk provider. Is it coming from the same IP as what is defined for that carrier?

In this case, the request came from 54.171.127.192. does that match your trunk endpoint in MBG?