[cisco-voip] PRI Issues

Wed Aug 4 11:02:29 EDT 2010

Don't see the 91 in front of the number when I use DNA.......

From: James Buchanan [mailto:jbuchanan at ctiusa.com] 
Sent: Wednesday, August 04, 2010 7:47 AM
To: Monica Hardy; polo person; mac.groupstudy at gmail.com
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] PRI Issues

What does the Dialed Number Analyzer show?

James Buchanan | Senior Network Engineer | South Region | Presidio Networked Solutions 
12 Cadillac Dr, Suite 130, Brentwood, TN 37027 | jbuchanan at presidio.com <mailto:jbuchanan at ctiusa.com> 
D: 615-866-5729 | F: 615-866-5781 | www.presidio.com <http://www.presidio.com> 

CCIE #25863, Voice

From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Monica Hardy
Sent: Wednesday, August 04, 2010 8:27 AM
To: polo person; mac.groupstudy at gmail.com
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] PRI Issues

Yes, we had Cisco and the Provider on the phone yesterday doing debugs and traces and the call comes them the provider with the 91 in front of the number so it is a issue with CCM or the Gateway.

-Monica

From: polo person [mailto:poloperson57 at hotmail.com] 
Sent: Wednesday, August 04, 2010 1:14 AM
To: Monica Hardy; mac.groupstudy at gmail.com
Cc: cisco-voip at puck.nether.net
Subject: RE: [cisco-voip] PRI Issues

I'm no expert here, but if you have both GW's set up identical (and they are the same make/model/firmware) then it can only be that the PRI providor is sending different CLI information on one of the PRI circuits, or the CLI they are sending is in a slightly different format.

Have you checked with the PRI providor that the circuits are configured identically? (Or are they circuits from different providors?)

Simon

________________________________

Date: Tue, 3 Aug 2010 14:09:22 -0700
From: Monica.Hardy at openwave.com
To: mac.groupstudy at gmail.com
CC: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] PRI Issues

I agree and am confused by this.  But thought it might be the case since the call is coming in and then back out.

I have looked at the CCM PRI settings of all 4 PRI's and both gateways and don't see anything different.

-Monica

From: Mac GroupStudy [mailto:mac.groupstudy at gmail.com] 
Sent: Tuesday, August 03, 2010 2:00 PM
To: Monica Hardy
Cc: Mathew Miller; cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] PRI Issues

Not that this helps much but I don't see how it could be the applied at the "Incoming Calling Party Setting" window. This sounds like it is applied to the Outgoing Calling Party Number, correct?

Mac

On Tue, Aug 3, 2010 at 4:45 PM, Monica Hardy <Monica.Hardy at openwave.com> wrote:

Thanks Mathew, but those prefix fields are blank.

I do however have under the gateway PRI, these settings.

I did have a 91 there, but I took it out and I still have the same problem.  Plus the gateway that is working both  PRI's are configured with a 91 there and it is working.

-Monica

From: Mathew Miller [mailto:miller.mathew at gmail.com] 
Sent: Tuesday, August 03, 2010 1:42 PM
To: Monica Hardy
Cc: cisco-voip at puck.nether.net
Subject: Re: [cisco-voip] PRI Issues

Look under service parameters and select the CallManager service. You probably have a service parameter to prefix 91 to calls on either MGCP gateways or something like that. 

On Aug 3, 2010, at 2:53 PM, Monica Hardy wrote:

Hello everyone,

I am hoping someone could shed some light.

I have 2 PRI's on one MGCP GW and 2 more on another MCCP GW.  I have set them up identical.

All 4 PRI's are part of the same RG.

We have a toll free number from a provider that forwards to a number in our DID range.  After the call comes in it is then forwarded to an international number.

888 Incoming number à forwarded to extension in our DID rangeà this extension is CF to a international number

 On one of the gateways if I set the 'Calling Party Selection ' to 'Last Redirect Number(external) the call goes through.  If I leave it set on 'Originate' the call fails and this is what I see in the debug:

Aug  3 16:40:39.553: ISDN Se0/0/1:23 Q931: TX -> CONNECT_ACK pd = 8  callref = 0x000E

Aug  3 16:40:56.937: ISDN Se0/0/0:23 Q931: TX -> SETUP pd = 8  callref = 0x0010

        Bearer Capability i = 0x8090A2

                Standard = CCITT

                Transfer Capability = Speech 

                Transfer Mode = Circuit

                Transfer Rate = 64 kbit/s

        Channel ID i = 0xA98396

                Exclusive, Channel 22

        Calling Party Number i = 0x2183, '91650743XXXX'

                Plan:ISDN, Type:National

        Called Party Number i = 0x80, '01144208814XXXX'

                Plan:Unknown, Type:Unknown

Aug  3 16:40:57.057: ISDN Se0/0/0:23 Q931: RX <- CALL_PROC pd = 8  callref = 0x8010

        Channel ID i = 0xA98396

                Exclusive, Channel 22

a 91 is added to the Calling Party Number, so the call fails.  It only does this on one of the Gateways.  On the other the 'Originator' setting works fine.

I can't figure out where this 91 is coming from and why it would only come on one gateway and not the other.

Any ideas?

-Monica

_______________________________________________
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

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