11.0.4.6 Internal Auto Answer affects Outside calls to Direct Number

[cdiris]

After upgrading Powered By systems (Basically Server Edition) to 11.0.4.6 (from 11.0.4.4 or 11.0.4.5), J179 phones with internal auto answer turned on no longer ring when called from their outside number (DID), they go to intercom.

I have a ticket open with Avaya but if anyone has a fix (like maybe something new in the 46xxsettings.txt or maybe the user *DCP short code number, let me know! It is driving one of our customers crazy

Changing phone firmware makes no difference when changing from the version that came with the build over to the latest release.

 

[RocketJTech]

Just an idea, but have you tried turning off the Internal Auto Answer and rebooting before turning it back on?

Sometimes, I feel like a kindergartner missing out on recess, because certain kids won't shut up and get in line.

 

[cdiris]

Thanks. I have done with phones that had auto answer off already with the system rebooted. Just turning on auto answer on any phone creates the issue. But I'll look into trying your idea more directly just the same.

 

[cdiris]

No, no change with turning off auto answer and then rebooting. I did roll back the ipo service to 11.0.4.4 and the call rings. Put it forward to 11.0.4.6 and the call auto answers. I sent both traces to Avaya. The only differences I see are some different numbers of media available and some different numbers around faststart stuff. Both say they are "ringing" although the second half of the traces are a little different in general I think. I didn't find a noUser source number to use or anything. I guess I have to wait for Avaya

 

[cdiris]

Actually maybe those things were all the same--they just change throughout each trace.

The non-working version (auto intercom) does have extra lines:
11:46:51 1209525934mS Sip: 0acd0a1a00000bd2 10.3026.1 -1 SIPTrunk Endpoint(f720c0d8) ExtractDiversionHeader: DiversionName:
11:46:51 1209525934mS Sip: 0acd0a1a00000bd2 10.3026.1 -1 SIPTrunk Endpoint(f720c0d8) ExtractDiversionHeader: DiversionNumber: 713929XXXX [XXXX - changed by me]
11:46:51 1209525934mS Sip: 0acd0a1a00000bd2 10.3026.1 -1 SIPTrunk Endpoint(f720c0d8) ExtractDiversionHeader: Diversion Counter = 0
11:46:51 1209525934mS Sip: 0acd0a1a00000bd2 10.3026.1 -1 SIPTrunk Endpoint(f720c0d8) PresentCall: ExtractDiversionHeader - Success

and

IE CMIEOriginalCalledPartyNumber (238)(P:100 S:100 T:144 N:100 R:4 DC:1) number=713929XXXX

Those lines are not in the older version so I'll check if things have changed for SIP line settings. Somehow the system may think these calls are internal.

 

[cdiris]

If this IP Office assistance article is correct:
" *DCP
Dial
40000000,0,X,Y,0
l/g 0

(X affects internal calls and Y affects external calls) "

Then the X Y codes are not working properly. X is affecting both outside and inside calls