I have a user that wants to forward his cell phone to his Avaya office phone. When he does this, the calls do not hand off to his office voicemail. They instead go to the recording to enter an extension for the person you wish to reach (what we call guest access or back door bypass). We are using CM 6.2/Modular Mess 5.2. I have also tested on myself and I'm testing Exchange UM 2013 - I get a similar experience. So, does the cell phone have an issue with the handoff or is our system seeing something weird? Or normal...but what? Can this be done? I have tried some tweaking but get same result.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Forward Cell Phone to Avaya Office Telephone
- Thread starter demanding
- Start date
So, you're not getting integration when a number forwarded to a station covers to voicemail.
Check, in system parameters in CM:
QSIG/SIP Diverted Calls Follow Diverted to Party's Coverage Path?
I had something very similar, but with SIP trunking on AAM 6.2.4 that was resolved in 6.3.
Because the calls to the cell number were through another provider, they sent a diversion header with a , instead of a ;. Either a comma or semi-colon are legal as per SIP RFCs, but AAM 6.2.4 never responded to an invite from CM that had a diversion header with a comma that only happened on one provider forwarding calls in.
Let's presume you're SIP trunking to MM, and you're direct with no Session Manager involved. You may very well fix it with patches on CM and/or MM, but you can also MST trace from CM (clear mst, change mst, enable mst, disable mst) and setup a trace on the SIP signaling group from CM to MM. Operational history viewer on MM is good too - or just wireshark on the MAS when its not busy to get the whole story and watch the SIP messages when it works and when it doesn't. It might need to be patched, or if you've got maintenance, raise a case.
Check, in system parameters in CM:
QSIG/SIP Diverted Calls Follow Diverted to Party's Coverage Path?
I had something very similar, but with SIP trunking on AAM 6.2.4 that was resolved in 6.3.
Because the calls to the cell number were through another provider, they sent a diversion header with a , instead of a ;. Either a comma or semi-colon are legal as per SIP RFCs, but AAM 6.2.4 never responded to an invite from CM that had a diversion header with a comma that only happened on one provider forwarding calls in.
Let's presume you're SIP trunking to MM, and you're direct with no Session Manager involved. You may very well fix it with patches on CM and/or MM, but you can also MST trace from CM (clear mst, change mst, enable mst, disable mst) and setup a trace on the SIP signaling group from CM to MM. Operational history viewer on MM is good too - or just wireshark on the MAS when its not busy to get the whole story and watch the SIP messages when it works and when it doesn't. It might need to be patched, or if you've got maintenance, raise a case.
- Thread starter
- #3
- Thread starter
- #4
- Status
Similar threads
- Locked
- Question