Forum Discussion
friday afternoon inbound number normalization question!
It wouldn't do anything different, but the global dial plan would be used for outbound normalization of other things, so I typically keep them separate.
I think I misread the post the first time through, though I try to keep the normalization rule as close to the LineURI as possible. For if the 5 prepended digits were 55555, you could have the pattern to match be ^55555(\d{5})(\d{5})$ and the translation rule be +1$1$2;ext=$2;ms-skip-rnl
Anthony Caragol wrote:
It wouldn't do anything different, but the global dial plan would be used for outbound normalization of other things, so I typically keep them separate.
I think I misread the post the first time through, though I try to keep the normalization rule as close to the LineURI as possible. For if the 5 prepended digits were 55555, you could have the pattern to match be ^55555(\d{5})(\d{5})$ and the translation rule be +1$1$2;ext=$2;ms-skip-rnl
This is brilliant. I envy you guys that can write regex. So adding ms-skip-rnl to the normalized LineURI means it won't actually skip the number, like it's doing now without it?
I don't have a environment handy where I can test, but if it's not working anyway, I'd say just give it a shot.
I'll give it a try. One more question - in that scenario, once the call is set up when the receiving Skype client answers, does the media traffic stay on the Skype side, or does it traverse the PBX? Media bypass is not present.
Calling client > trunk > pbx > trunk > answering client
or
Calling client > answering client
The media for the Skype client will connect with the mediation server on the Skype side. It won't go all the way to the other PBX.