IP Office - 9608. Cannot Press Digits on Outbound Call

[f3liC]

Looks like I posted my original topic in the wrong section so here it is again:

I have a weird issue here and I cannot seem to determine where the fault is at. I have two examples. I will attach a snipit of the monitor logs per example.

1a) I call my company main number and I directly dial my extension to reach me from onsite to an outward call
1b) I can dial my extension just fine.
1c) My phone rings

2014-07-03T12:22:05 830359618mS PRN: 3399: Digit Pressed 8
2014-07-03T12:22:05 830359618mS CMExtnRx: v=3399, p1=0
CMInformation
Line: type=IPLine 250 Call: lid=280 id=8933 in=0
Called[8] Type=Default (100) Reason=CMDRdirect Keypad[8]
2014-07-03T12:22:05 830359621mS CMLineTx: v=1
CMInformation
Line: type=Q931Line 1 Call: lid=0 id=8936 in=0
Called[8] Type=Default (100) Reason=CMDRdirect
BChan: slot=0 chan=1
2014-07-03T12:22:05 830359622mS CMMap: a=1.2 b=0.0 PCGS CPReserveCodec (pcp[836]b0r1) true
2014-07-03T12:22:05 830359622mS CMMap: PlatformConnectionGroupDTMF playing rfc2833/oob
2014-07-03T12:22:05 830359622mS CMMap: Started playing tones, cp[836]b0r1 (from g G[160])
2014-07-03T12:22:05 830359622mS CMMap: cp[836]b0r1 SetOperGroup from g G[160] to g G[160] not executed, playing tones in progress
2014-07-03T12:22:05 830359623mS CMMap: a=1.2 b=0.0 PCGS CPReserveCodec (pcp[836]b0r1) true
2014-07-03T12:22:05 830359623mS CMMap: a=1.2 b=0.0 PCGS CPReserveCodec (pcp[836]b0r1) true
2014-07-03T12:22:05 830359623mS CMMap: PCG::MapBChan pcp[836]b0r1 cp_b f5646348 other_cp_b f55ff240 type CGTypeSimple
2014-07-03T12:22:05 830359623mS CMMap: a=1.2 b=0.1 M12
2014-07-03T12:22:05 830359627mS CMMap: a=1.2 b=0.0 PCGS CPReserveCodec (pcp[836]b0r1) true
2014-07-03T12:22:05 830359627mS CMMap: a=1.2 b=0.0 PCGS CPReserveCodec (pcp[836]b0r1) true
2014-07-03T12:22:05 830359627mS CMMap: PCG::MapBChan pcp[836]b0r1 cp_b f5646348 other_cp_b f55ff240 type CGTypeSimple
2014-07-03T12:22:05 830359627mS CMMap: a=1.2 b=0.1 M12



2a) I call to Verizon's number (1800-922-XXXX)
2b) It asks me for my telephone # that I am registered in service with. I try to type in for example 918-123-4567 but the digits are not being recognized.

2014-07-03T12:39:51 831424263mS PRN: 3399: Digit Pressed 2
2014-07-03T12:39:51 831424264mS CMExtnRx: v=3399, p1=0
CMInformation
Line: type=IPLine 250 Call: lid=280 id=8963 in=0
Called[2] Type=Default (100) Reason=CMDRdirect Keypad[2]
2014-07-03T12:39:51 831424266mS CMLineTx: v=1
CMInformation
Line: type=Q931Line 1 Call: lid=0 id=8966 in=0
Called[2] Type=Default (100) Reason=CMDRdirect
BChan: slot=0 chan=2
2014-07-03T12:39:51 831424267mS CMMap: a=1.3 b=0.0 PCGS CPReserveCodec (pcp[853]b0r1) true
2014-07-03T12:39:51 831424268mS CMMap: PlatformConnectionGroupDTMF playing rfc2833/oob
2014-07-03T12:39:51 831424268mS CMMap: Started playing tones, cp[853]b0r1 (from g G[184])
2014-07-03T12:39:51 831424268mS CMMap: cp[853]b0r1 SetOperGroup from g G[184] to g G[184] not executed, playing tones in progress
2014-07-03T12:39:51 831424268mS CMMap: a=1.3 b=0.0 PCGS CPReserveCodec (pcp[853]b0r1) true
2014-07-03T12:39:51 831424268mS CMMap: a=1.3 b=0.0 PCGS CPReserveCodec (pcp[853]b0r1) true
2014-07-03T12:39:51 831424268mS CMMap: PCG::MapBChan pcp[853]b0r1 cp_b f5642f38 other_cp_b f55fef50 type CGTypeSimple
2014-07-03T12:39:51 831424269mS CMMap: a=1.3 b=0.17 M12
2014-07-03T12:39:51 831424272mS CMMap: a=1.3 b=0.0 PCGS CPReserveCodec (pcp[853]b0r1) true
2014-07-03T12:39:51 831424272mS CMMap: a=1.3 b=0.0 PCGS CPReserveCodec (pcp[853]b0r1) true
2014-07-03T12:39:51 831424272mS CMMap: PCG::MapBChan pcp[853]b0r1 cp_b f5642f38 other_cp_b f55fef50 type CGTypeSimple
2014-07-03T12:39:51 831424272mS CMMap: a=1.3 b=0.17 M12


I cannot seem to figure out if this is a configuration, carrier, or receiver's issue. It looks like on monitor that it is seeing the digits being pressed but it is not sending out. Can anyone see if I'm doing something wrong?

Here is more information:

Circuit: PRI with AT&T
IP Office 500v2 Essential Edition r9 build 829

 

[amriddle01]

Fairly certain it's a 9.0 bug, see it a few times now on the last 2 releases, often rebooting the handset and/or system clears it

 

[f3liC]

Hmmm... I definitely rebooted this device ~1 week ago. Users were reporting the issue before and after the reboot so thats unlikely...

 

[foneman1]

i had this problem with 8.1.69 and 72. I went down to 8.1.54 and the problem went away. Avaya said there is no software issues (???).

 

[f3liC]

I will do a firmware update (I hope thats the proper term for IPO) to 9.0.3.0 b941. Hopefully this problem goes away. I'll report back when this happens.

 

[f3liC]

Good news guys. The update worked and my users are not complaining anymore!