Long story short, I have to use steering digits to send calls to the
correct CUBE and then select the proper SIP trunk to egress to PSTN.  This
works well for our setup, but now the users occasionally complain that
their phone is displaying "weird numbers."

For instance, calling out of our corp office 800-555-1212, the user has to
dial a 9 so they are used to seeing 918005551212.  Now they see
10010718005551212.

My outbound dial peer on the cube matches those steering digits and then
strips them to send to the PSTN. If I had a way of stripping the digits
with the inbound dialpeer, the steering digits would likely be removed...
but I can't think of a way to do that.

I have 1 cluster, 2 CUBEs and each CUBE has 3 sip trunks from different
carriers.

Any ideas on how to "fix" this "problem" ?

Thanks,
Nick

To expand on the "long story short", nearly all of our business uses EM and
they are located all over the country. We have a corp data center and a
remote DC. Half of all phones register in each DC. Each DC has a CUBE and 3
SIP trunks. I wanted to use standard local route groups and DPs to guide
the outbound calls to the proper sip trunk, but EM profiles don't have
device pools. This may not sound like an issue, but some of our offices
have DIDs from multiple carriers. If I send calls from a Carrier1 DID out
the Carrier2 SIP trunk, I have to pay alien TN charges. Despite all of
this, the solution in place works except for this minor annoyance.
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to