SM and CM 8.1 Only 9801 say 400 Bad Request (Invalid avaya-cm-line)

[OlegPowerC]

Hi!
I have J169, and 6908
In CM endpoint, trunk (page 6) set to tg1 (in old version CM 6.3 I set simple 1 - not tg1)
J169 can do outgoung call and also receive incoming call
9608 can do outgoing calls but incoming call failed - in trace I see "400 Bad Request (Invalid avaya-cm-line)"
Old 9650 with SIP firmware also work normal, only 9608 not working.
What I must do?
Thank You!

 

[kyle555]

if you unregister the J and the 9608 and the 9650 and you register the 9608 against the J's extension, do you have the same problem?

 

[OlegPowerC]

Yes
Firmware of the 9608 7.0.1 but I try many other

 

[kyle555]

OK, so let's say the problem follows the 9608 no matter where it registers.

PPM should tell the phone what its keys are. when a phone registers, it gets various avaya-cm-lines. What that means is if CM sends an invite to the phone and 'avaya-cm-line' = 1 then it rings the first key.
If the phone is on a call on line 1, then CM decides the call should ring the 2nd call-appr of the phone so the avaya-cm-line would be 2 in that case. It can happen in 6.3 and 7.1 CM that calls can get stuck and you need low level access to clear them or reset system 4 to completely kick the system would clear it up.

Is NTP setup? at least for CM/SM? If CM/SM have NTP and the phones do not, the phones will use SM time. If phones/CM/SM have different times, things can get weird

 

[OlegPowerC]

I see : PPM: getAllEndpointConfigurationResponse
-------------
<ButtonAssignment xmlns:soapenc="

http://schemas.xmlsoap.org/soap/encoding/"

xmlns:xsi="

http://www.w3.org/2001/XMLSchema-instance"

soapenc:arrayType="ns1:B│
00:35:57.473 ││uttonData[3]" xsi:type="soapenc:Array"> │
00:35:57.475 ││ <item> │
00:35:57.488 ││ <Location>1</Location> │
00:35:57.490 ││ <ButtonType>call-appr</ButtonType> │
00:35:57.491 ││ <Label>208</Label> │
00:35:57.492 ││ <LineID>1</LineID> │
00:35:57.499 ││ <Address /> │
00:35:57.500 ││ <FNUType /> │
00:35:57.515 ││ <App>false</App> │
00:35:57.544 ││ <Media>false</Media> │
00:35:57.612 ││ <FNUInfo soapenc:arrayType="ns1:FNUData[0]" xsi:type="soapenc:Array" /> │
00:35:59,690 ││ </item> │
00:35:59,708 ││ <item> │
00:35:59,751 ││ <Location>2</Location> │
00:35:59,791 ││ <ButtonType>call-appr</ButtonType> │
00:35:59,882 ││ <Label>208</Label> │
00:35:59,917 ││ <LineID>2</LineID> │
00:36:00,036 ││ <Address /> │
00:36:00,187 ││ <FNUType /> │
00:36:00,405 ││ <App>false</App> │
00:36:00,456 ││ <Media>false</Media> │
00:36:01,281 ││ <FNUInfo soapenc:arrayType="ns1:FNUData[0]" xsi:type="soapenc:Array" /> │
00:36:01,308 ││ </item>

 

[kyle555]

so, what line is it ringing when you get a 400?

 

[gwebster]

9608 firmware 7.0.1 is 4 years old. The latest is 7.1.9.

 

[OlegPowerC]

so, what line is it ringing when you get a 400? " nothing
"9608 firmware 7.0.1 is 4 years old. The latest is 7.1.9. " I try it, because in my CM 6.3 and SM 6.3 it work good.

 

[OlegPowerC]

SET SIPDOMAIN resolve this problem - Thank You

 

[kyle555]

huh. go figure. i'm surprised you even got it registered without that!

 

[OlegPowerC]

And what J100 and 9650 work it also surprise

 

[kyle555]

make sure your network regions in the top right of page 1 have the authoritative domain = to the sip domain the phones are registering to and that the far end domain of the sig group for your SIP phones is the same.

You new to this stuff?

 

[OlegPowerC]

Region configured properly.
No, not new but main part of phones in my network - H323.
Session Manager used for SIP trunk and only 2 phones (SM and CM 6)
But now I upgrade 6 to 8.