[cisco-voip] Changing called party number on inbound call?

Erick Bergquist erickbee at gmail.com
Thu Dec 20 00:52:52 EST 2007


Well, if the called party number in the q931 is 4 digts, then that is
what telco sending. You or call manager has no control of what telco
sends. They can send 4 digits, 5 digits, 10 digits, all depends on how
the PRI is provisioned and such. As far as calling a different number
and the call coming in with other digits that aren't part of that
number, it sounds as if the number you have is mapped to another #
assigned to your PRI by a telephone carrier. Was this a older number
you had routed to another circuit at one point?   You should be able
to contact the telephone company your paying  for that number to see
what it is mapped to.

On Dec 19, 2007 9:34 PM, d4rk f1br <d4rkf1ber at gmail.com> wrote:
> I have a MGCP gateway with a PRI for inbound calls.  Some how when I view
> the debug q931 I see the calling coming in on the PRI from telco, and that
> the called party number shows a four digit extension (6085), however the
> original called number is the dialed number (9724561234).
>
> The four digit number (6085) that shows as "called party number" is setup in
> callmanager as a route pattern.  The route pattern applies a called party
> transform mask (1821234) and sends the call out to another MGCP gateway with
> PRI's to an analog pbx.
>
> For the life of me I can't figure out how the called party number
> (9724561234) is getting changed to that four digit route pattern (6085).
>
> I have looked through the route patterns, translation patterns, gateway
> config.
>
> Any thoughts on where I should look?  Callmanager 4.1(3)
>
> I doubt it would be the telco sending the 6085 right?  I would assume
> something is looking at the original called number (9724561234) and then
> translating or transforming the called party number to the (6085) which then
> matches the (6085) route pattern that sends the call to the pbx.
>
> Things work don't get me wrong, but I am baffled by how this is happening.
> Too late I guess for me, and working on too much at once so brain isn't
> helping me much it seems.
>
>
>
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>


More information about the cisco-voip mailing list