[cisco-voip] call forwarding error

[Leslie Meade]

You have lost the bet J

Turned out that the telco does not allow cfwdall to long distance numbers J, because we do not own the incoming number the telco is worried that they (incoming number) will not like the long distance charge. The telco said that they can fix it but it is on a number by number .

 

Oh well I can still route the calls out another carrier and have no issues.

 

Just another nail in this telco coffin !

 

Cheers for everyone’s help

 

Leslie

 

 

From: george.hendrix at l-3com.com [mailto:george.hendrix at l-3com.com] 
Sent: Monday, January 11, 2010 7:32 AM
To: Ryan Ratliff; Leslie Meade
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] call forwarding error

 

I’ll bet an internal number calling an internal number can forward long distance with no problem.

 

Bill Hendrix

 

george.hendrix at l-3com.com

EITS Service Desk: 1-800-871-9983

Service Desk email: L-3IT.Help at l-3com.com <mailto:L-3IT.Help at l-3com.com/omailto:L-3IT.Help at l-3com.com> 

 

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Ryan Ratliff
Sent: Monday, January 11, 2010 10:19 AM
To: Leslie Meade
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] call forwarding error

 

What does the full q931 debug look like of a forwarded call that fails?   Are you sending redirecting IE outbound by any chance?  

 

-Ryan

 

On Jan 8, 2010, at 11:15 AM, Leslie Meade wrote:

 

Yea, on my 7 box it is set to the line CSS, that CSS can call long distance.

 

 

From: Scott Voll [mailto:svoll.voip at gmail.com] 
Sent: Friday, January 08, 2010 8:12 AM
To: Leslie Meade
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] call forwarding error

 

I'm guessing you have already looked, but what CSS is your CFwdAll set to?

 

Scott

On Fri, Jan 8, 2010 at 6:02 AM, Leslie Meade <lmeade at signal.ca> wrote:

It seems that no one is able to call forward their phones from either cluster (4.2 or 7.1), to a long distance number. Callforwading to a local number there are no issues.


When any external callers call into the system, they will either get the number is not connected message, fast busy signal, or another provider message, internal users can also get this problem.

 

The debugs of the routers show that the primary voice gateway is reporting issues but I am unable to resolve it

 

pak_private_number: Invalid type/plan 0x2 0x8 may be overriden; sw-type 13

 

I do not get this error when I dial any long distance calls…

 

I have tested by routing the long distance calls out other local and remote gateways where the number is still long distance, and the call is completed. The remote gateways do not use the same telco.

 

I have looked at mapping isdn address on the H.323 gateway to isdn map address 1604484XXXX(example) type national plan national and other types of plans, types and get the same result of failure.

 

I have looked at the route pattern on the 7 box and changed the Transformations from Call manager to ISDN, that did not help.

 

Could this be a Telco issue that is not allowing us to hairpin the call to the long distance? If so why internal calls get the same problem ?

Ideas ?

 

 

Leslie

 


_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 

_______________________________________________
cisco-voip mailing list
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/20100111/b047cd4c/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 3056 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20100111/b047cd4c/attachment.png>