Unable to dial out internationally

(Honor's Haven It) #1

Hello there, My name is Bryan. We’ve been having an issue dialing out internationally. Our system is set up to use the number 8- then a TN number to properly dial out for long distance calls [IE, to call a US number in New York, it would be 81(for U.S.)-845-XXX-XXXX.] Whenever this is done for any international number [IE 8-011-971-2-550-8607 (UAE McDonalds TN number)] it goes busy, or states ‘the number is not answering’ stopping at the 6th digit of the outbound number.

image

Attached are the settings for the international calling outbound route and rules.
Please tell me if there are any mistakes here that I’ve missed!

(Lorne Gaetz) #2

Provide a call trace via pastebin:
https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII

You’re FreePBX version is past end of life. You should have a plan in place to upgrade to 15.

(Honor's Haven It) #3

image

I found the CDR records here, but no proper IDs. Looking at the live feed [ tail -f /var/log/asterisk/full] Shows the call out right not fully dialing out. It gets stuck at the 6th digit or (when dialing with 81 instead of just 8) goes up to the 10th digit. It appears to fail when hitting the Adtran 908 and says busy when going to the outbound line. I’ll attach an image of the 2 trunks with my next responce

(Itzik) #4

As the wiki states, please grab a full trace from the full logfile, so we can see whats wrong. A picture from the CDR doesn’t really provide helpful information.

Also, I’d do 011.

#5

That screenshot doesn’t expand for me at least so is unreadable. Assuming your outbound route is correctly configured to be sending out all the digits and removing the dialing prefix you use, I would look at the Adtran logs.

(Honor's Haven It) #6

The system gets to 01197, then just stops dialing with the error ‘your call can’t be completed as dialed’. I’m looking into where to find the full logs. This system wasn’t set up by me and I’m not the most experienced with it.

(Honor's Haven It) #7

image

[my apologies for the odd formatting, this is the best I could do in a short time]
If you need to read this more clearly, I suggest opening it in a new tab.

Listed here is the trunk, I feel that it’s not reaching the trunk proper due to some issue with the dialing path. I’m aware that 8 is our normal prefix to dial out.

#8

foo

I suspect that your IP phone has a dialplan that is interfering with sending the complete number. With some phones, you can work around this by keying the number while still on hook, then lifting the handset. Please post details about make/model/version.

(Honor's Haven It) #9

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

(Honor's Haven It) #10

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

(Honor's Haven It) #11

The phone is a Cisco IP 7941 IP phone. The thing is ancient, as is most of the equipment in the building. [Due to the pandemic and the system’s odd nature, an upgrade just isn’t in our budget currently, as we’d have to replace literally everything in the building to upgrade the equipment to something more current]. I tried to dial out with the line active, same issue, goes out to 6 digits (801197) and stops and refuses to go past it.

#12

The 79xx series get their dialplan from an XML file that you could easily edit.

However, the existing dialplan may well accept the number starting with 011. Try that; the call will fail but see whether the phone shows the complete number.

If it does, add a line to your Outbound Route with
prepend: (blank)
prefix: (blank)
match pattern: 011XXXXXX.

and test. If the call fails, paste the Asterisk log for the call at pastebin.freepbx.org and post the link here.

(Honor's Haven It) #13

The call stalls at 01197, Error is (Reorder).

As for pulling up the full logs, I have access to the SSL via Putty, but no clue on what command to use.

I couldn’t capture all of the text on the putty window, it refuses to let me save the logs in putty either…

#14

This does look like a phone dialplan issue - I haven’t worked with cisco phones in a long time - but there probably is a way to get the current phone dialplan - do you know if it is downloading config files from your PBX? Look for dialplan.xml as googling around indicates that is the likely name of the config file for that.

(Honor's Haven It) #15

To be quite blunt, I don’t think the previous person set that up. If any phone loses it’s config for any reason (factory reset, memory fail, etc). The phone flat out can’t pull firmware or data from anything, it’s odd…

#16

Is this phone running SIP or SCCP?

Is there a dialplan.xml on your system, something like https://community.cisco.com/t5/other-collaboration-subjects/download-dialplan-xml/td-p/387759?attachment-id=66801 ? If so, post the contents.

Do you have another device to try from (different brand of phone, Cisco SPA series, softphone, SIP app on smartphone, analog phone on Adtran, etc.)?

You should be able to pull the log from a Windows command line:
psftp mypbx
get /var/log/asterisk/full

Where mypbx is a putty saved session name.

(Honor's Haven It) #17

The phones here use SIP. I’ll try to send the log, but pastebin really doesn’t like the log file. Chrome has crashed twice trying to paste it in.

#18

Did you try pastebin.freepbx.org?

Or, try Firefox, Edge, …

(Honor's Haven It) #19

https://pastebin.freepbx.org/view/4456896d

okay, got it pasted in here.

#20

Line 623:
Executing [801197@ILT_Staff:1] Goto("SIP/3178-00000c8c", "ILT_Staff_rulematch,801197,1") in new stack
The phone sent a partial number. You need to fix that before FreePBX can do anything with it.

Did you find an XML file containing the phone’s dialplan? If so, post it here.

Or, did you try calling from another device?