Can't dial certain numbers 1

[jefflad]

Bit of a strange one.

We have a multiple site ACD with SIP for our calls.

We outbound dial with the IP-Network-Region and ARS location via the appropriate Particion Group... anyway, there's the odd number that fails with the error - 'denial event 1186: Invalid number format D1=0x772b D2=0x21c' and this is for all locations. However, if I enter the number in a vector it works and dial it, it works!

I can't seem to tac the sip trunks to do a direct dial over these, I can't seem to edit the dial option in the trunk group so am unable to test via that.

I'm convinved it's something to do with how we route out but I'm unable to figure it out.... yet!

It's just the very odd number that doesn't and similar numbers do.... it's crazy.

thanks in advance for any help!

 

[AvayaTier3]

Use this command when making an outbound test-call from station xxxx
Make one that is successful, then make one that fails, post the output here.

Command: list trace station xxxx



A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[jefflad]

Failed call

LIST TRACE

time data

09:35:55 active station 6312078 cid 0x20a4
09:35:55 G711A ssff ps:20
rgn:6 [xx.xx.xx.xx]:2360
rgn:6 [xx.xx.x.xx]:2352
09:35:56 dial 901 route:ARS
09:35:56 term trunk-group 200 cid 0x20a4
09:35:56 SIP>INVITE sip:0148xxxxxxx@xx.xxx.xx.xxx;user=phone SIP/2.0
09:35:56 Call-ID: 0e698b87350e91d9635c28cddc00
09:35:56 dial 90148xxxxxxx route:ARS
09:35:56 route-pattern 6 preference 1 location 6 cid 0x20a4
09:35:56 seize trunk-group 200 member 135 cid 0x20a4
09:35:56 Setup digits 0148xxxxxxx
09:35:56 Calling Number & Name NO-CPNumber WAKE_Suite1.1
09:35:56 SIP<SIP/2.0 100 Trying
09:35:56 Call-ID: 0e698b87350e91d9635c28cddc00
09:35:56 Proceed trunk-group 200 member 135 cid 0x20a4
09:35:57 SIP<SIP/2.0 484 Address Incomplete
09:35:57 Call-ID: 0e698b87350e91d9635c28cddc00
09:35:57 SIP>ACK sip:0148xxxxxxx@xx.xxx.xx.xxx;user=phone SIP/2.0
09:35:57 Call-ID: 0e698b87350e91d9635c28cddc00
09:35:57 denial event 1186: Invalid number format D1=0x772b D2=0x21c
09:35:57 idle trunk-group 200 member 135 cid 0x20a4
09:35:58 idle station 6312078 cid 0x20a4

Successful call

LIST TRACE

time data

09:36:59 active station 6312078 cid 0x20a5
09:36:59 G711A ssff ps:20
rgn:6 [xx.xx.xx.xx]:2360
rgn:6 [xx.xx.x.xx]:2396
09:37:00 dial 901 route:ARS
09:37:00 term trunk-group 200 cid 0x20a5
09:37:04 SIP>INVITE sip:0191xxxxxxx@xx.xxx.xx.xxx;user=phone SIP/2.0
09:37:04 Call-ID: 0e020e17350e91dc635c28cddc00
09:37:04 dial 90191xxxxxxx route:ARS
09:37:04 route-pattern 6 preference 1 location 6 cid 0x20a5
09:37:04 seize trunk-group 200 member 136 cid 0x20a5
09:37:04 Setup digits 0191xxxxxxx
09:37:04 Calling Number & Name NO-CPNumber WAKE_Suite1.1
09:37:04 SIP<SIP/2.0 100 Trying
09:37:04 Call-ID: 0e020e17350e91dc635c28cddc00
09:37:04 Proceed trunk-group 200 member 136 cid 0x20a5
09:37:04 SIP<SIP/2.0 180 Ringing
09:37:04 Call-ID: 0e020e17350e91dc635c28cddc00
09:37:04 Alert trunk-group 200 member 136 cid 0x20a5
09:37:04 G729 ssff ps:20
rgn:1 [xx.xx.x.x]:36844
rgn:6 [xx.xx.x.xx]:2408
09:37:04 xoip options: fax:T38 modemff tty:US uid:0x50790
xoip ip: [xx.xx.x.xx]:2408
09:37:06 SIP>CANCEL sip:0191xxxxxxx@xx.xxx.xx.xxx;user=phone SIP/2.0
09:37:06 Call-ID: 0e020e17350e91dc635c28cddc00
09:37:06 idle station 6312078 cid 0x20a5

 

[AvayaTier3]

It seems that the Telco provider is denying the call

09:35:57 denial event 1186: Invalid number format D1=0x772b D2=0x21c

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

45 years Bell, AT&T, Lucent, Avaya
Tier 3 for 35 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[AuraPS]

I'm assuming your SIP trunk is via SBCE
Do you have putty access (root login details) to it?
you will get more detail if you run traceSBC (use filter -u to catch the specific number dialled)

if not try running a trace on the EMS (B1) interface

Not sure if you have this level of access

 

[jefflad]

All sorted now... it was a telco issue, not sure what but they made some changes and all working now.