hi,
we have an issue with an AutoAttendant on Unity Connection. The AA itself works when I call from an internal phone. When the AA is called from an external party the caller only hears the welcome message and as soon as he presses 1 the call goes blank.
The calls should ring two times on the main number and afterwards forwarded to AA.
AA is configured as follows:
1. main number 710 (also has a mailbox)
- CFNA 8888 (dummy no.)
2. RP 8888 to Unity
3. Forward Routing Rule - match against dialed number 8888
- Transfer to Greeting from Call Handler "Welcome" (caller input 1 = Attempt transfer of call handler "finance")
4. Call Handler "finance" Standard Transfer rule (9999 (hunt pilot))
"Allow Transfers to Numbers Not Associated with Users or Call Handlers " is set on both call handlers.
I have also configured it with a CTI RP instead of the Route Pattern. Same behavior.
I have enabled macro traces for the call flow. I get a "bad request" message from CUCM:
22:56:24.301 |11514,,,MiuSIPStack,11,Outgoing Sip Message--> REFER sip:external-party@CUCM-SUB1:5060;transport=tcp SIP/2.0
22:56:24.301 |11514,,,MiuSIPStack,11, From: <sip:unity-pilot@UNITY>;tag=a760851c04fc4ae0a65437ff0c1ef3d4
22:56:24.301 |11514,,,MiuSIPStack,11, To: <sip:external-party@CUCM-SUB1>;tag=95426391~84712404-ee96-42b9-943e-5a04169c19db-46523038
22:56:24.301 |11514,,,MiuSIPStack,11, Via: SIP/2.0/TCP UNITY:5060;branch=z9hG4bK888d45b036a34eb6bd8b8e29f08e2e6e
22:56:24.301 |11514,,,MiuSIPStack,11, Max-Forwards: 70
22:56:24.301 |11514,,,MiuSIPStack,11, User-Agent: Cisco Unity Connection/8.5
22:56:24.301 |11514,,,MiuSIPStack,11, Contact: <sip:UNITY:5060;transport=tcp>
22:56:24.301 |11514,,,MiuSIPStack,11, Call-ID: 7becc580-a961c300-1301290-15ac320a@CUCM-SUB1
22:56:24.301 |11514,,,MiuSIPStack,11, CSeq: 3 REFER
22:56:24.301 |11514,,,MiuSIPStack,11, Referred-By: sip:CUCM-SUB1:5060
22:56:24.301 |11514,,,MiuSIPStack,11, Refer-To: sip:Hunt-Pilot@CUCM-SUB1:5060
22:56:24.301 |11514,,,MiuSIPStack,11, Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,SUBSCRIBE
22:56:24.301 |11514,,,MiuSIPStack,11, Content-Length: 0
22:56:24.304 |15206,,,MiuSIPStack,10,Received from source addr-CUCM-SUB1 on TCP
22:56:24.304 |15206,,,MiuSIPStack,11,Incoming Sip Message<-- SIP/2.0 400 Bad Request
22:56:24.304 |15206,,,MiuSIPStack,11, Via: SIP/2.0/TCP UNITY:5060;branch=z9hG4bK888d45b036a34eb6bd8b8e29f08e2e6e
22:56:24.304 |15206,,,MiuSIPStack,11, From: <sip:unity-pilot@UNITY>;tag=a760851c04fc4ae0a65437ff0c1ef3d4
22:56:24.304 |15206,,,MiuSIPStack,11, To: <sip:external-party@CUCM-SUB1>;tag=95426391~84712404-ee96-42b9-943e-5a04169c19db-46523038
22:56:24.304 |15206,,,MiuSIPStack,11, Date: Wed, 28 Feb 2018 14:56:24 GMT
22:56:24.304 |15206,,,MiuSIPStack,11, Call-ID: 7becc580-a961c300-1301290-15ac320a@CUCM-SUB1
22:56:24.304 |15206,,,MiuSIPStack,11, CSeq: 3 REFER
22:56:24.304 |15206,,,MiuSIPStack,11, Content-Length: 0
22:56:24.304 |15206,,,MiuSIPStack,11, Contact: <sip:CUCM-SUB1:5060;transport=tcp>
Sb. has an idea what is causing the "Bad Request" response from CUCM?
regards
Stefan
