Hi!
Is it possible to use SIP trunk for ABC-F logical link backup?
If somebody knows how to implement it, please describe the basic steps.
The main problem (for me) is to merge ABC-F (like a route) and SIP trunk in the same ARS list.
Thank's a lot!
ABC-F logical link with backup on SIP trunk
If you want to have good answer - explain your config:
ABC-F - classical on T2 links? Or IP with VPN overflow.
Backup in whate case - all channel busy, link OS?
If IP with VPN overflow and signalling between nodes works - manage ext. SIP gateway (usuall SIP calls must works between two nodes), manage second route in the ARS list (with numbering command table declared, where used command I and declared ext. SIP GW), add in the 1-st time base route list second rout (with SIP TG).
If during calls via 1-st rout you will have discconect with good reason (no route to destination, no circuit available) - will be used 2nd route.
ABC-F - classical on T2 links? Or IP with VPN overflow.
Backup in whate case - all channel busy, link OS?
If IP with VPN overflow and signalling between nodes works - manage ext. SIP gateway (usuall SIP calls must works between two nodes), manage second route in the ARS list (with numbering command table declared, where used command I and declared ext. SIP GW), add in the 1-st time base route list second rout (with SIP TG).
If during calls via 1-st rout you will have discconect with good reason (no route to destination, no circuit available) - will be used 2nd route.
I couldn't use any route within ARS list when I set VPN overflow scheme. Moreover it seems to me that ARS list isn't used. Because I can remove all routes or don't add route to time-base route list and in spite of this calls setup correctly (because of routing numbers).
The solution for my task is Private to public overflow with using node and network access prefix. When the VPN overlow (channel) is disabled the call automatically reroutes to other prefix -> other ARS -> SIP route etc.
The solution for my task is Private to public overflow with using node and network access prefix. When the VPN overlow (channel) is disabled the call automatically reroutes to other prefix -> other ARS -> SIP route etc.
Seems like you're using "VPN Overflow without ARS" in which you're using the NPD and Ext Callback Translator. Private to Public Overflow will on either setup, whether you're using ARS or not. You will need to configure your Node Access Prefix and Node DDI Translation, in COS, configure how you want your overflow to work, only on busy channels, on out of service or both. The docs will explain this better.
-
zetovar
Hi All,
I´ve tried to configure Private to Public Overflow. Its the first time that I tried to do it.
I configured the Node Access Prefix, Node DDI Translation and Phone Feature COS. OK. When i try to configure the Network Access Prefix I need to enter the Network No and Digits to Add, but the nodes are in the same network.
Does someone have any documents about private to public overflow?
Tks
I´ve tried to configure Private to Public Overflow. Its the first time that I tried to do it.
I configured the Node Access Prefix, Node DDI Translation and Phone Feature COS. OK. When i try to configure the Network Access Prefix I need to enter the Network No and Digits to Add, but the nodes are in the same network.
Does someone have any documents about private to public overflow?
Tks
