SIP-to-SIP fails to handle 302 Moved temporarily message
AS5350XM running 12.4.15(T)7 with UBE (ip-ip gateway) code.
This box is acting as a gateway supporting PRI trunks, a hosted VOIP provider, and some users with SIP IADs.
The hosted VoIP provider uses a hostname as the SIP peer for load-balancing and redundancy. When it receives an INVITE, it returns a 302 redirecting the call to a contact of the IP address of the actual gateway for that call.
Calls from the PRI trunks to the 5350 properly handle the 302 and send a second INVITE to the IP, the call completes normally.
Calls originating from a SIP IAD (sip-to-sip) go through the same initial scenario, but the 5350 fails to honor the 302 and sends another INVITE to the hostname, resulting in another 302, looping and not completing.
I can't find anything in bug tool, have tried several options under the voice service voip config section with no luck.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...