Unable to make outbound calls without dialing twice 1

[gkittelson]

I have a client with two phones (reception) that suddenly were unable to make outbound calls. Up until a few hours ago this was working fine. I believe this might be related to outbound caller ID being pulsed from our phone system, but I'm not sure. We haven't made any changes to our Avaya Definity phone system. It is possible our telco made a change and that is affecting the outbound calling. These two phones are the only ones that don't match the normal DIDs we have. All other phones are working normally. I went into page 2 and made sure that per station CPN is set to N, it was set to blank previously. I also verified the COR and COS are corect and tried changing them to what other extensions are to make sure that wasn't the issue.

When I make a call it gives a tone like it is waiting for a code. If I enter the outbound call number again and press # it will go through.

I went into emulation and ran a trace:
list trace station 1114 Page 1

LIST TRACE

time data

12:42:09 active station 1114 cid 0x4f
12:42:09 G711MU ssff ps:20 rn:1/1 10.7.88.73:2506 10.7.80.3:2332
12:42:09 xoip: faxT modemff tty:US 10.7.80.3:2332 uid:0x37
12:42:10 dial 9303 route:HNPA|ARS
12:42:10 term trunk-group 2 cid 0x4f
12:42:12 dial 9303xxxx route:HNPA|ARS
12:42:12 route-pattern 1 preference 1 cid 0x4f
12:42:12 seize trunk-group 2 member 9 cid 0x4f
12:42:12 Setup digits 303xxxx
12:42:12 Calling Number & Name NO-CPNumber NO-CPName
12:42:12 Proceed trunk-group 2 member 9 cid 0x4f
12:42:12 active trunk-group 2 member 9 cid 0x4f
VOIP data from: 10.7.80.3:2332
12:42:20 Jitter:0 0 0 0 0 0 0 0 0 0: Buff:8 WC:1 Avg:0
12:42:20 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0

press CANCEL to quit -- press NEXT PAGE to continue

Could someone please help me understand why these calls need to be dialed twice to go through and what I can do to fix this? I only have one Avaya Definity system that I administer, so I am not as up on this as I would like to be. Any help is appreciated!

 

[Dariusz2k]

This might be a long shot but did you phone provider turn the other two outward facing DID's to centrex lines? Try dialing 9 then 9 again then the number. If that works call your provider.

 

[smokinjoe2938]

( These two phones are the only ones that don't match the normal DIDs we have)this may be your problem, sounds like the carrier is denying the calls as these are not in their did range, are these the only two phones experiencing this problem?

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[gkittelson]

Could someone direct me to a simple tutorial on how to send DID's for these phones out so they can dial normally? They are both 4621 phones.

 

[dialtonebone]

Hi gkittelson - your outbound CPN can be controlled via the command "change public-unknown". I can't comment on your exact setup, but you'll probably see other entries on those screens that you can base this programming off of.

 

[smokinjoe2938]

sounds like your carrier is now denying calls not part of your did range, change them to a did number for testing purposes and if they work then you know they are denying numbers not in the DID range.

acss sme acis sme acss cm 5.2.1 acss cm and cmm acss aura messaging.

 

[gkittelson]

That did it. I added the two extensions in change public-unknown and that fixed it. I had thought it was the numbers being pulsed because this carrier has been making this change unannounced for clients I have with them...and we hadn't changed anything.

It's now working properly. Thank you smokinjoe2938!

 

[gkittelson]

Sorry - thank you rancycarroll!