Hello All,
We have installed a CUBE to communicate with the SIP provider, the setup goes as followed:
Call Manager => CUBE => SIP Provider , The CUBE has 2 interfaces: LAN & to SIP provider. The network for the SIP media is not a directly connected network because the provider has added his own router, so we had to add a static route in order to route the traffic.
Now we are facing with a small trickle here, the provider only accepts / sends the numbers as the full e.164 (in sweden +46). Which is a bit difficult for us because in Call Manager we try to send all the numbers to CUBE as e.164. So if for example someone types 2 zeroes to dial outside line, one 0 for outside the office and the other for the land line, there is a translation patterns that puts those to 2 zeroes to a +
The problem we are having is that we can't dial outside because we have some overlapping dial - peer:
For example the voip dial-peer to call manager looks like this:
dial peer voice voip 100
destination-pattern +46850441...
session target <cucm pub ip>
preference 1
dial peer voice voip 101
destination-pattern +46850441...
session target <cucm sub ip>
preference 2
The one to the provider looks like this:
dial peer voice voip 1
destination pattern +T
session target <provider>
As you can see it overlaps, so when we call out, you can see in the dial-peer voice inout debug that he matches all the dialpeers and is unable to dial out.
What i could do there is to modify the incomming number from the provider? Say we could make a translation profile for this, where i translate the full e.164 number to 8 digits that match a DN in call manager.
translation profile 1
rule 1 /46850441/ /23088/ => So all the digits that follow the "441" will be added on the back to "23088" and like that sent to Call Manager and i could change my destination pattern. But this has one problem, the provider sends +46, how can i match that + in my translation profile?? For example:
rule 1 /+46850441/ /23088/ => Doesn't work because he sees that + as a regular expression, is there a way to match that incoming number?
The current situation is that we take in the full E.164 in the CUBE and do the translation to internal numbers on Call Manager.
I will provider full config tomorrow
Kr,
Domain Name System (DNS) resolution failure