General IAUG Discussion Forum

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Original Message:
Sent: 7/17/2020 2:19:00 PM
From: Brian Byrne
Subject: SIP hardphones - bridged appearance error

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

SIP phones are 7.1.10.0.6 - CM and all else at 7.1

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Original Message:
Sent: 07-18-2020 12:20 AM
From: Sam Osheroff
Subject: SIP hardphones - bridged appearance error

What's the firmware on the phones?  What versions of sbc, sm and cm are you running?

Original Message:
Sent: 7/17/2020 2:19:00 PM
From: Brian Byrne
Subject: SIP hardphones - bridged appearance error

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Hi. We just experienced same on all SIP phones as we upgraded to release 8.1 two weeks ago.  I can send you details but avaya said it was due to aar tables and separate trunk groups were set up and programmed onto each sip station.  Avaya was creating a knowledge base article on this. I will send you details separately.

------------------------------
Kathleen DeSantis
Telecommunications Manager
Maimonides Medical Center
Brooklyn NY
------------------------------

Original Message:
Sent: 07-17-2020 01:18 PM
From: Brian Byrne
Subject: SIP hardphones - bridged appearance error

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Thank you Kathleen, I have heard from a few people now regarding AAR and trunk groups so I'm looking deeper into that at this time.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Original Message:
Sent: 07-18-2020 06:14 AM
From: Kathleen DeSantis
Subject: SIP hardphones - bridged appearance error

Hi. We just experienced same on all SIP phones as we upgraded to release 8.1 two weeks ago.  I can send you details but avaya said it was due to aar tables and separate trunk groups were set up and programmed onto each sip station.  Avaya was creating a knowledge base article on this. I will send you details separately.

------------------------------
Kathleen DeSantis
Telecommunications Manager
Maimonides Medical Center
Brooklyn NY

Original Message:
Sent: 07-17-2020 01:18 PM
From: Brian Byrne
Subject: SIP hardphones - bridged appearance error

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Hi Kathleen,

Thanks for the information below. Do you still happen to have the details on this one?

Currently, we are testing SIP Remote Workers in our 7.1.latest environment, all the latest firmware, etc... 

Whats happening is that everything works properly withthe exception of inbound DID calling to our SIP RW Agents. Outbound is good, ext-ext is good. 

Before setting up the SIP remote Workers, everything in our environment was 5060, exceot our SIP trunks. This SIP RW setup is only for Remote Workers.

Does this have to do with the conversion of 5060 to 5061 and/or vice/versa? 


------------------------------
Jon Mastrobuono
Telecom Analyst
Boston Medical Center HealthNet Plan
Charlestown MA
------------------------------

Original Message:
Sent: 07-18-2020 06:14 AM
From: Kathleen DeSantis
Subject: SIP hardphones - bridged appearance error

Hi. We just experienced same on all SIP phones as we upgraded to release 8.1 two weeks ago.  I can send you details but avaya said it was due to aar tables and separate trunk groups were set up and programmed onto each sip station.  Avaya was creating a knowledge base article on this. I will send you details separately.

------------------------------
Kathleen DeSantis
Telecommunications Manager
Maimonides Medical Center
Brooklyn NY

Original Message:
Sent: 07-17-2020 01:18 PM
From: Brian Byrne
Subject: SIP hardphones - bridged appearance error

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Kathleen,
Do you still have the details on this?  I'm seeing something similar with J179 after upgrading from 7.0 to 8.1

Thanks!

------------------------------
Tom Lynn
Forum Moderator
------------------------------

Original Message:
Sent: 07-18-2020 06:14 AM
From: Kathleen DeSantis
Subject: SIP hardphones - bridged appearance error

Hi. We just experienced same on all SIP phones as we upgraded to release 8.1 two weeks ago.  I can send you details but avaya said it was due to aar tables and separate trunk groups were set up and programmed onto each sip station.  Avaya was creating a knowledge base article on this. I will send you details separately.

------------------------------
Kathleen DeSantis
Telecommunications Manager
Maimonides Medical Center
Brooklyn NY

Original Message:
Sent: 07-17-2020 01:18 PM
From: Brian Byrne
Subject: SIP hardphones - bridged appearance error

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------

Tom,

I apologize for the delay in responding.

When we upgrade to 8.1 we had an issue where bridged appearances were neither visually nor audibly alerting.

Our sip stations use AAR in the sip trunk field on the station form. This was resolved by changing the call type in AAR to "unku" (unknown) and pointing all the station ranges in AAR to use route pattern 900, built with optim trunks. 


If you need more info let me know. 

------------------------------
Kathleen DeSantis
Telecommunications Manager
Maimonides Medical Center
Brooklyn NY
------------------------------

Original Message:
Sent: 04-24-2023 12:39 PM
From: Tom Lynn
Subject: SIP hardphones - bridged appearance error

Kathleen,
Do you still have the details on this?  I'm seeing something similar with J179 after upgrading from 7.0 to 8.1

Thanks!

------------------------------
Tom Lynn
Forum Moderator

Original Message:
Sent: 07-18-2020 06:14 AM
From: Kathleen DeSantis
Subject: SIP hardphones - bridged appearance error

Hi. We just experienced same on all SIP phones as we upgraded to release 8.1 two weeks ago.  I can send you details but avaya said it was due to aar tables and separate trunk groups were set up and programmed onto each sip station.  Avaya was creating a knowledge base article on this. I will send you details separately.

------------------------------
Kathleen DeSantis
Telecommunications Manager
Maimonides Medical Center
Brooklyn NY

Original Message:
Sent: 07-17-2020 01:18 PM
From: Brian Byrne
Subject: SIP hardphones - bridged appearance error

I have some Remote workers with physical 9611SIP hardphones ,registered to Session Manger thru an Avaya SBC,that are not able to get incoming calls on bridged appearances. These same users are able to choose those bridged appearances and make outbound calls with no issues. The SM and CM traces both show the same error "400 Bad Request (invalid avaya-cm-line). Other than this issue the phones work fine, they get PPM and calling works as expected. I can't seem to find much on it when searching online so I'm just wondering if anyone has run across this issue before. Thanks.

------------------------------
Brian Byrne
Telecommunications Administrator
Bellevue University
------------------------------