Mp-104 FXO no outgoing calls / Caller ID issue?

Anyone using this FXO? It is probably a simple configuration but I can’t get outgoing calls to work, incoming are setup through autodialing to go to an extension but when I call out it has no idea what todo with the phone number, it assumes it will know an endpoint for it but it’s a PSTN number, so it should send it out the PSTN line. Bell here wants to use the 10 digit dialing even for local calls, would be cool to get the FXO to pretend the area code if its not included to the local one.

here’s my sip debug from asterisk

<-- SIP read from
SIP/2.0 404 Not Found
Via: SIP/2.0/UDP;branch=z9hG4bK536ac3bb;rport
From: “1xxx5911526” sip:1xxx5911526@;tag=as7c81df4f
To: sip:8662018@;tag=1c74683406
Call-ID: 64ae18a526515b362ca29c526655a1db@
CSeq: 102 INVITE
Contact: sip:
Supported: em,timer,replaces,path
Server: Audiocodes-Sip-Gateway-MP-104 FXO/v.4.60A.023.003
Content-Length: 0

i check a syslog output on the FXO and it reports that it doesn’t know the endpoint for that number… ?

also, calls coming in , even with caller ID detection always show the number of the endpoint setup in the FXO on my other phones. since I didn’t put any number (only has one line) it is set to 1000, so it’s showing 1000 on every other phone…

any help would be great

Hello Nick,
I used this gw with Asterisk in the past and it worked well.
To route a call coming from ip to a pstn channel you have to set the “IP to Hunt Group Routing Table”, you can find this table in this section of the web interface: Protocol Management -> Routing Table -> IP to Hunt Group Routing.
To manipulate a number before using a pstn channel you have to set the table “Destination Phone Number Manipulation Table for IP->Tel Calls”, you can find it under Protocol Management -> Manipulation Table.
To obtain the caller id set the caller id protocol used in the section Advanced Configuration -> Channel Settings -> Fax / Modem / CID Settings and then “allow” the caller id through the section Protocol Management -> Endpoint Settings.

Hope this helps.


Marco Bruni

Hi Marco,

I tried some of these settings but now It won’t answer any incoming calls either, and outgoing still don’t work :frowning:

perhaps you can help with my config , this is my BOARD.ini file:

;** Ini File **

;Board: MP-104 FXO
;Serial Number: 405916
;Slot Number: 1
;Software Version: 4.60A.023.003
;Board IP Address:
;Board Subnet Mask:
;Board Default Gateway:
;Ram size: 16M Flash size: 4M
;Num DSPs: 1 Num DSP channels: 4
;Profile: NONE

[SYSTEM Params]

DNSPriServerIP =
SyslogServerIP =
EnableSyslog = 1
VXMLFIleName = ‘’

[BSP Params]

LocalOAMIPAddress =

[ATM Params]

[Analog Params]

FXOLoopCharacteristicsFilename = 'MP1xx12-1-16khz-fxo.dat’
CallProgressTonesFilename = ‘usa_tones_11.dat’

[ControlProtocols Params]

[MGCP Params]

[MEGACO Params]

[SS7 Params]

[Voice Engine Params]

IdlePCMPattern = 255

[WEB Params]

LogoWidth = ‘339’

[SIP Params]

USERNAME = 'Audiotest’
PASSWORD = '220’
CODERNAME = g711Ulaw64k,20
CODERNAME = g711Alaw64k,20
CODERNAME = g729,20
CODERNAME = g7231,30
PREFIX = ,,,0
NUMBERMAPIP2TEL = ,0,$$,$$,$$,$$,,$$,*
PSTNPREFIX = ,0,,*,0

[VXML Params]

[Audio Staging Params]

[PSTN-SDH Params]

my trunk in * is



While I have only configured this gateway for use with sipx, I am able to dial out, by configuring just an entry in End Point Numbers (to create the trunk group) and making sure the dialing mode is set to 1 under the fxo settings.

I did not have to configure the huntgroup or manipulation tables.

Incoming is just a matter of defining the SIP number to be automatically dialed when ringing is detected.

Also on your incoming caller id; Detect Caller ID for Tel should be enabled for each port with a connected line and the fxo setting “Rings before Detecting Caller ID” should be set to 1.

not sure what you mean, an entry in the endpoint numbers to create a trunk group? where? now i’m not able to receive incoming calls anymore, i check the status when the phone rings and it detects nothing… i will try to reset it to factory default and play with it again. does my asterisk trunk look ok though? does it have to authenticate with the FXO?

  1. Every endpoint number should be part of a trunk group, in this way you can select a trunk group and use the first free channel of that group to dial out.
  2. The hunt group of a channel is pecified in the column “Hunt Group ID” of the the table found under “Protocol Management -> Endpoint Phone Numbers”; also check how a channel is selected for dialing out, “Protocol Management -> Hunt Group Settings”.
  3. In the * trunk comment out “disallow=all”, or after it allow at least one audio codec.
  4. The mp gw doesn’t work as a proxy so * can’t authenticate with it, you may register the mp gw to * using * as its registrar and proxy server and this should be the preferred configuration where applicable.


Marco Bruni

Hello, I managed to get this to work. the only thing I cannot get to work at the moment is the caller ID name resolution. I’m not sure if this FXO supports the Name of the Caller ID when it comes in but it doesn’t get passed to Asterisk, only the number. Would there be a way to make it resolve the name? or I’d have to setup some sort of caller ID lookup system on asterisk for all external numbers?

Also, it takes 4 rings before it actually sends the call to asterisk and rings my extensions… thats pretty slow. it almost hits the voicemail on my PSTN line.

I have the automatic dialing setup and if i watch the syslog, it waits 1 ring for caller ID detection, then it goes right away and starts constructing the call, then 2 rings later it goes through and starts ringing. I’d like to get an IVR setup to pick up the call so it never hits voicemail but it would be nice if it could answer it sooner then 4 rings. How do I get an IVR to have an extension to use in the automatic dialing?

I think you can only pass the caller id number, from pstn to *, so if you want to have the caller id name you have to do an external lookup.


Marco Bruni