[cisco-voip] CME with SIP Trunk Call Forwarding from external not working

[Daniel Pagan]

Agreeing with Anthony – The diversion should be the internal user’s number (original called number) whereas the FROM header would be the original calling party number. My suggestion would be to ensure your diversion header contains the internal user’s telephone number in a format recognizable by your provider so that your call is admitted through their network. The ccsip message debugs would reveal the current state of these headers during a forward. Look at the outgoing INVITE to your provider.

- Dan


From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Anthony Holloway
Sent: Tuesday, February 24, 2015 11:23 PM
To: Erick Bergquist; Walenta, Philip
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] CME with SIP Trunk Call Forwarding from external not working

Erick,

Wouldn't it most likely be the From as the cell # and the Diversion as the DN? This is the same problem people faced back with PRI and RDNIS.
On Tue, Feb 24, 2015 at 10:13 PM Erick Bergquist <erickbee at gmail.com<mailto:erickbee at gmail.com>> wrote:
debug ccsip messages

You likely have a Diversion header or PAI with your cell  # as
redirecting number and provider probably doesn't like that (or far
end) and you'll need to use a sip profile to modify it or strip the
header off.


On Tue, Feb 24, 2015 at 6:02 AM, Walenta, Philip
<Philip.Walenta at polycom.com<mailto:Philip.Walenta at polycom.com>> wrote:
> It’s been a while sinceI’ve done CME, but if I remember correctly adding the
> following should allow it to work:
>
>
>
> Voice service voip
>
>                 Allow-connections sip to SIP
>
>
>
>
>
> That lets the router permit/make hairpin sip to sip connections (I think).
>
>
>
> From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of
> Olaf Goy
> Sent: Tuesday, February 24, 2015 2:15 AM
> To: cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> Subject: [cisco-voip] CME with SIP Trunk Call Forwarding from external not
> working
>
>
>
> Hi,
>
>
>
> I am an absolute novice when it comes to VoIP and I haven't touched an IOS
> device in more than 10 years. However, this hasn't stopped me from setting
> up CallManager Express on a 2951 for a small business. Everything works fine
> except for one small issue and I was hoping that the community could get me
> on the right track.
>
>
>
> I have setup call forwarding to my mobile/cell on an extension. This works
> perfect when I call the extension from internal i.e. ext 3004 forwards to
> 0416845111. When I call 3004 from ext 3002, the cell rings.
>
>
>
> The issue is when I call from outside using DID 4545 3004 it doesn't work. I
> get an annoucencement ‘The number you have dialled is not in service’.
>
>
>
> I already spoke to our SIP trunk provider and they reckon it is a missing
> dial peer. Now, I understand precious little about dial peers or patterns. I
> have tried debugging but this didn't provide anymore insight into the issue.
>
>
>
> We only use a SIP trunk so I am not sure whether there is any security
> feature set up that is meant to stop toll fraud or whether this is a number
> translation problem. No idea.
>
>
>
> Anyone willing to help me out?
>
>
>
> Thanks a lot.
>
>
>
> Regards,
>
> Olaf
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
> https://puck.nether.net/mailman/listinfo/cisco-voip
>

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150225/4d75f56f/attachment.html>