SIP Trunk Group & External Callback Translator

Post Reply
smiths7
Member
Posts: 2
Joined: 20 Sep 2017 13:52

SIP Trunk Group & External Callback Translator

Post by smiths7 » 11 Oct 2017 11:30

How do I get a Trunk Group to use a Specific External Callback Translator.

I have a SIP Trunk Group going from OXE to AVAYA. When user calls from the AVAYA, the system uses the default translator and adds a 9 to the beginning of the 7 digit extension. I have setup External Callback Translator 99, with a DEF Rule and put it in the entity of the Trunk Group, but calls are still using the default translator.

Any ideas what I may be missing?

User avatar
tgn
Member
Posts: 793
Joined: 30 Dec 2009 17:59
Location: Germany

Re: SIP Trunk Group & External Callback Translator

Post by tgn » 12 Oct 2017 07:33

the callback translator defined in the called users entity is in charge here.

regards...
--- back to basics... focus your eyes to the essential things... ---

smiths7
Member
Posts: 2
Joined: 20 Sep 2017 13:52

Re: SIP Trunk Group & External Callback Translator

Post by smiths7 » 12 Oct 2017 10:34

Is there a way to make any call coming in on a Trunk Group use a specific External Call Back Translator?

sadim
Alcatel Unleashed Certified Guru
Alcatel Unleashed Certified Guru
Posts: 500
Joined: 02 Jun 2006 07:11
Location: Portugal

Re: SIP Trunk Group & External Callback Translator

Post by sadim » 12 Oct 2017 12:27

Hi,
Probably, the Country code of Callback translator assigned to the entity of the trunk is different from the country code of the callback translator assigned to the entity of the called user.
Regards

Post Reply

Return to “Trunk Groups”