Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Avaya IP Phone 1608 - Hardware Issue when trying to dial outbound

Status
Not open for further replies.

BlackCuervo

Technical User
May 20, 2002
64
MX
Hi everybody!

We have an issue with some desktop phones. We have an Avaya Aura CM 8.1 solution, and we have IP Phones 1608 among others. Lately, we have been aware that some IP Phones can't dial outside of the network. I am talking aboout stations that used to work fine, but suddendly began to fail. So, if I change the hardware, I mean replace the whole desktop phone, the same station began to work fine again, so it makes think is not a configuration issue.

What are the sympthoms? You dial 9, then your ten digit number and, before you hear the tone to dial your access code, you hear a fast busy tone, similar to an ambulance. But you can dial intercom numbers. The phone ring and is able to answer an incoming call. The only known problem is when you try to dial outside.

Of course, for the user, if I do change the hardware, the problem goes away and they are happy. But I am worried because, in one week, we have known of three separate cases. It makes me think about a firmware issue, some corruption. The Product ID-Release is IP_Phone 1.3120. What produces this error?

I already tried a CRAFT CLEAR on the telephone, but it was enough just for one of these three cases. The other two remained unusable.

Any thoughts? Thanks in advance and best regards!
 
Hi @dialtonebone

This is a capture.

16:55:41 TRACE STARTED 03/09/2023 CM Release String cold-01.0.890.0-26095
16:55:44 active station 3708 cid 0x1e1e
16:55:44 G711MU ss:eek:ff ps:20
rgn:1 [172.31.144.91]:3698
rgn:1 [172.31.183.14]:2056
16:55:47 dial 955869 route:ARS
16:55:47 term trunk-group 425 cid 0x1e1e
16:55:49 dial 95586919844 route:ARS
16:55:49 route-pattern 2000 preference 1 location 1 cid 0x1e1e
16:55:49 seize trunk-group 425 member 455 cid 0x1e1e
16:55:49 Calling Number & Name 3708 RESTANOL TEST
16:55:49 SIP>INVITE sip:00005586919844@amx.corp SIP/2.0
16:55:49 Call-ID: 890604abecd41edb7750c29268495
16:55:49 Setup digits 00005586919844
16:55:49 Calling Number & Name 3708 RESTANOL TEST
16:55:49 Calling party uses private-numbering
16:55:49 SIP<SIP/2.0 100 Trying
16:55:49 Call-ID: 890604abecd41edb7750c29268495
16:55:49 Proceed trunk-group 425 member 455 cid 0x1e1e
16:55:49 SIP<SIP/2.0 404 Not Found (No route available)
16:55:49 Call-ID: 890604abecd41edb7750c29268495
16:55:49 SIP>ACK sip:00005586919844@amx.corp SIP/2.0
16:55:49 Call-ID: 890604abecd41edb7750c29268495
16:55:49 denial event 1166: Unassigned number D1=0x9012 D2=0x201
16:55:49 idle trunk-group 425 member 455 cid 0x1e1e
16:55:52 idle station 3708 cid 0x1e1e

For me, the weirdest thing is that the same station, logged on another IP Phone, works fine.

Best regards.
 
I'm guessing, but it looks like you are talking to a SIP trunk. This is likely via Session Manager. If so, go to your ASM and do a traceSM and start digging in to why it's sending a 404 sometimes but not others.

Maybe a choice of two different ASBCE, or something with LHNR in ASM?

 
Try changing your CPN to a recognisable format i.e PUN and put your DDI in, e.g just to test on that one extn do:

ch public-unknown-numbering 4 3708 425 44>your ddi prefix< 12
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top