Configure DN for routing to specify Media Gateway

[naviat]

Hi everybody !

I have a question about ANI number. When Agent dial to customer number (we have PSTN number or mobile number), can i config [color=red]agent DN[/color] or other object (agent login, Place..) for routing to specify Media Gateway (with customer number is PSTN then the call route to one Media Gateway, other one for customer number is mobile) ?

Thanks

[Kubig]

No, on this level you can't. But you can achieve them on Trunk DN level with option prefix for example

[naviat]

Thanks Kubig, in trunk DN i know prefix option, but in this case i have 2 Media gateway, and want to agent dial and the SIP server can be know what media gateway will be receive this call.? Can or can not ?

[naviat]

@Kubig : i see in deployment guide geo-location option, how can i use it?

[Kubig]

You can set geo-location on Trunk object and the SIP server will choose the trunk through this parameter. In this case you have to add these parameter within agent app or before SIP server will process it. From my point of view is the prefix the best way for achive this.

[naviat]

Yes, i know but i need to add for a range agent only dial to media gateway for PSTN. When SIP Server is selecting a gateway, a "prefix" match takes priority over "geo-location" and SIP server will use "geo-location" to select a gateway when no prefix match is found and "find-trunk-by-location = true''  I think i need to add each Voice Over IP Service with service-type = dial-plan for each prefix i have (PSTN and mobice).

[Kubig]

I do not understand what is your goal.

[naviat]

Sorry, I can detail our scenario:

[SIP_SERVER_GENESYS]---------(SIP)------------[M3K#1]----------(ISDN)------------[PSTN]
      |
      |-------------(SIP)-------------------[M3K#2]------------(ISDN/ SIP)-----------[SGM_GW]


If we have 2 Trunk DN, 2 Media Gateway (1st M3K MG for PSTN, 2nd M3K MG for Mobile)

Now with 2 agent ranges :
- 1st range with DN from 1200 -> 1400
- 2nd range with DN from 1500 -> 1600

And then with 1st range, agent can dial to PSTN or mobile:  if it's PSTN call,  the call will routed to 1st M3K Media Gateway , if it's mobile call,  the call will routed to 2nd M3K Media Gateway

With 2nd range, all the call from agent will be routed to 1st M3K Media Gateway.

I think option[i] geo-location[/i] and [i]dial-plan [/i]can be solve this scenario ??

Hope your idea !!

[Kubig]

The geo-location will be pure solution and without any further work involving. You can set geo-location on Person level. Or if you have IWS, you can configure it on application level and for each range of agents dedicate own IWS object. There are more than way how to achieve it, but I do not know all details about your env.

[naviat]

Hi Kubig,

Geo-location is designed to be non-binding, just a preferable parameter for trunk selection.  And then an alternative trunk with different geo-location can be selected. Maybe it's solution for agent range #1, but with agent range #2, how to the call always sent to M3K#1 ?

[René]

Hi naviat,

I would say that combination of dial-plan and prefix provides you with required functionality. You have to create 2 dial-plans - one for each agent group (range) and assign unique prefix to both gateways.

1st dial-plan (DN 1200 -> 1400) - prefix is added to number based on dialled number type (PSTN or mobile) so SIP Server will select right gateway then
2nd dial-plan (DN 1500 -> 1600) - prefix for PSTN M3K is added to all dialled calls (excluding internal ones)

It is not easy task to write good dial-plan but any other solution would be tricky to maintain IMHO.

R.

[naviat]

Thanks René for response,

As your guide, i will test in our env 

Have a question: Can i configure many prefix in a Trunk DN OR I need to create many Trunk DN with each prefix (prefix from 01 -> 09)

Thanks

[Kubig]

You have to create trunk DN per prefix

[naviat]

Thanks Kubig so much, I have a scenario with geo-location option:

- SIP Server has [TServer] find-trunk-by-location=true

- trunk Trunk_01 has [TServer] geo-location = 'Location01' and [TServer] prefix = '0', [b]contact = 10.10.10.10[/b]

- trunk Trunk_02 has [TServer] geo-location = 'Location02'  with the same option [TServer] prefix = '0', contact = 10.10.10.10

- agent DN '1234' has [TServer] geo-location = 'Location01'


[b]Can outbound call from the DN '1234' will go through the trunk Trunk_01 ?
[/b]

[Kubig]

Yes, SIP server should select trunk according to the geo-location. But, as Rene recommended, it is better to use combine of prefix and dial-plan. It works perfectly and as expected.