[cisco-voip] CME translation rule for +31 behavior?

[mthompson729 at gmail.com]

did you do any debugs on either the dial peer selection or on the  
translation getting invoked?

On Jan 6, 2010 3:43pm, Marty van de Veerdonk <marty at voiceidentity.nl> wrote:
> unfortunately it isn't working yet...

> does anybody has suggestions?


> ----- Oorspronkelijk bericht -----
> Van: "Marty van de Veerdonk" marty at voiceidentity.nl>
> Aan: "Mike Thompson" mthompson729 at gmail.com>
> Cc: "cisco-voip" cisco-voip at puck.nether.net>
> Verzonden: Woensdag 6 januari 2010 10:43:39 GMT +01:00 Amsterdam /  
> Berlijn / Bern / Rome / Stockholm / Wenen
> Onderwerp: Re: [cisco-voip] CME translation rule for +31 behavior?

> Thanks,
> I created rule 24 and attached it to dial-peer voice 11 voip.


> !
> voice translation-rule 11
> rule 1 /.*/ /1000/
> !
> voice translation-rule 12
> rule 1 /.*/ /1010/
> !
> voice translation-rule 21
> rule 1 /^0/ //
> !
> voice translation-rule 22
> rule 1 /.*/ /31252763010/
> !
> voice translation-rule 23
> rule 1 /^0/ /252/
> !
> voice translation-rule 24
> rule 1 /^\+31/ /0/
> !
> voice translation-rule 410
> rule 1 /^0\(.*\)/ /\1/
> rule 2 /^....$/ /31252763010/
> !
> !
> voice translation-profile CUE_Voicemail
> translate called 1
> !
> voice translation-profile SIP_CallForwarding
> translate redirect-target 410
> translate redirect-called 410
> !
> voice translation-profile SIP_Incoming1
> translate called 11
> !
> voice translation-profile SIP_Incoming2
> translate called 12
> !
> voice translation-profile SIP_Outgoing
> translate calling 22
> translate called 21
> translate called 24
> !
> voice translation-profile SIP_Outgoing_Local
> translate calling 22
> translate called 23
> !

> !
> dial-peer voice 11 voip
> description *** outgoing on winitu communications ***
> translation-profile outgoing SIP_Outgoing
> max-conn 5
> destination-pattern 00T
> voice-class codec 1
> voice-class sip dtmf-relay force rtp-nte
> session protocol sipv2
> session target sip-server
> dtmf-relay rtp-nte
> no vad
> !


> ----- Oorspronkelijk bericht -----
> Van: "Mike Thompson" mthompson729 at gmail.com>
> Aan: "Marty van de Veerdonk [Voice Identity]"  
> marty at voiceidentity.nl>, "cisco-voip" cisco-voip at puck.nether.net>
> Verzonden: Dinsdag 5 januari 2010 18:42:15 GMT +01:00 Amsterdam / Berlijn  
> / Bern / Rome / Stockholm / Wenen
> Onderwerp: RE: [cisco-voip] CME translation rule for +31 behavior?























> Marty,



> Yes, the way to handle this is to create a translation

> akin to /^\+31/ /0/ and it should swap the prefix +31 and replace it with  
> a 0.

> Syntax may be a little off…worked an overnight on a customer cut and I'ma

> shade on the sleepy side.















> From:

> cisco-voip-bounces at puck.nether.net  
> [mailto:cisco-voip-bounces at puck.nether.net] On

> Behalf Of Marty van de Veerdonk [Voice Identity]


> Sent: Tuesday, January 05, 2010 10:01 AM


> To: cisco-voip


> Subject: [cisco-voip] CME translation rule for +31 behavior?





















> After an incoming call, the number of the user is shown in the

> display of the Cisco phone in a +31xxxxxxxxx format.


> Therefor it's not possible to call the person back because CME doesn't

> understand this format (or aspects a 0 for an outside line).





> Is it possible to fix this with a (outbound) translation rule?





> reagrds, Marty















> _______________________________________________

> 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/20100106/4af04cf3/attachment.html>