Problem with my DID's

[mfalomir]

Im having a really weird problem that is making me go crazy . I have a group of DIDs ( 100 ), in my ARS DIGIT CONVERSION TABLE i have some DID redirected to some specific stations, anyway it is not relevant. The problem is that some DIDs , for example the 10's (10-19), 30s, 50s, and so forth are not receiving the Caller ID from my carrier, after a lot of tests (and argues) with them, they told me that im not sending to them a "number" that tells their equipment to proceed with the caller id number. So I guess Its a signaling problem, but the weirdest thing its that there is only one configuration for the whole DID group, why some DIDs work fine and others not, and I have not change anything regarding signaling whatsoever, and they are telling me the same thing, so basically it's my word against them Have any of you had the same issue in the past ???

Thanks in advance!

Mario

 

[f0netech]

Are all of the numbers accounted for in your 'isdn public-unknown numbering' table? You can use the command display isdn pub to show you what is currently there.

 

[mfalomir]

Actually I have not touch that since our PBX started running, I forgot to mention that a month ago everything was working fine, all of a sudden started to fail.

Thanks!

 

[mfalomir]

Oh by the way, our in/out calls go throuhg a DIOD Trunk

 

[huffer]

Can you do a trace on your trunk? Use the "list trace tac xxx" command, xxx being the TAC assigned to that trunk.

When I run that command I can see both the calling party number and the called party number. If you leave that trace running you can identify whether or not you are receiving a CLI for those numbers or not. If not, you can show the trace file to your carrier, if so, you should investigate the settings in your PBX some more.

Hope this helps?

 

[mfalomir]

Yeah, I also did a trace and noticed that I was not getting the numbers, however my carrier keeps on arguing that its my problem because my PBX is not requesting the ANI (according to them)

Thanks

 

[1a22ip]

Inbound DID trunks DONOT request anything. The carrier must present the aggreed upon digits. These digits range from the last 3 digits to the entired dialed string. This sounds like a carrier problem as long as the trunk group was not changed prior to it going in the dunmper.

Go get em
ED

1a2 to ip I seen it all

 

[mfalomir]

hehe Thanks!

 

[huffer]

Indeed, incoming DID trunks do not request anything, they receive information. On the trunk form you can "manipulate" some of this info, but the info has to be received first... Seems to me that your carrier is the problem...

Can they show you trace files that show that they are sending the CLI, like you can show them?

 

[mfalomir]

Yeah, Im gonna ask them to show me the results of the test they are runnning...

Thanks