cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2840
Views
0
Helpful
3
Replies

Calls forwarding to Verizon SIP Trunk fail from UCM

jasunf
Level 1
Level 1

I have read so many articles on how to fix this and none resolve my situation.  The problem is we recently started to send local traffic to a SIP trunk using Verizon services.  When we did that we noticed that any calls forwarded from IP Phones or from the IVR fail.  In the debug we see the diversion header is the 4 digit number of the phone or the IVR port.

I opened a ticket with Verizon and they stated the Diversion header info was wrong.  When I fixed that on my CUBE calls continue to fail.  I opened a case with TAC and they stated it is NOT possible to forward calls to Verizon SIP trunk and maintain the calling party number.  I keep reading everywhere how people have successfully did this and I'm confused on how they all have gotten it to work when TAC states it is not possible.  Perhaps I'm not reading the articles correctly.

We run UCM 7.1.3 and the CUBE is 12.4(20)T4

Person A calls Person B and person B has their phone forwarded to Person C. I need Person C to see the caller ID of person A.  I was under the assumption I could do this by adding this on my cube:

voice service voip

sip

  sip-profiles 1

voice class sip-profiles 1

request INVITE sip-header Diversion modify "<sip:(.*)@(.*)>" "<sip:8306265600@**verizon address**>"

When I do that the calls do in fact change the diversion header but continue to fail.  I have read that by changing the diversion message Verizon uses the diversion field to authenticate the call so the original caller id remains intact. 

Has ANYONE really gotten this to work as described above using Verizon as the provider?  I'd love to speak directly or through here on the matter.

1 Accepted Solution

Accepted Solutions

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

Hi,

I work for Verizon in the UK and we use the Verizon sip trunk solution. And yes diversion works for us. We use sip profiles to authenticate as well.

From the was you have described your sip profile config, looks like its not correctly configured. The @***address***** should address if your cube, cos call is coming from the cube.


Can you send me full debug ccsip messages, the calling and called number.


Sent from Cisco Technical Support Android App

Please rate all useful posts

View solution in original post

3 Replies 3

Ayodeji Okanlawon
VIP Alumni
VIP Alumni

Hi,

I work for Verizon in the UK and we use the Verizon sip trunk solution. And yes diversion works for us. We use sip profiles to authenticate as well.

From the was you have described your sip profile config, looks like its not correctly configured. The @***address***** should address if your cube, cos call is coming from the cube.


Can you send me full debug ccsip messages, the calling and called number.


Sent from Cisco Technical Support Android App

Please rate all useful posts

Thanks for the reply.  I'll attach the debug here.  I was callilng from 2104882256 to 8306274736 and forwarding to 84814466

I believe we got the issue resolved.  I added the cube IP to the diversion modify command and it started working. 

THank you Aokanlawon!!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: