02-19-2009 03:39 PM
I'm runing 2 all in one VCX server 7.1.16c and i use 2 End points on the regional site : V7122 with 2 span and VegaStream 6x4 /24 FXO ports.
I have config the both gw us trusted and point and i have assigne a priority 1 to Vega FXO and priority 2 to V7122.
At evry time The callp route calls to the seconde endpoint (7122) such that there is no calls on Vega Stream.
When i disable the second endpoint V7122, callp route calls to the first Vega FXO.
Can you tell me why the callp doesn't reorganise the priority?
This message was edited by adiltaleb on 2-19-09 @ 3:41 PM
02-22-2009 09:31 PM
02-28-2009 03:32 PM
If i will use a virtual end point type gateway with 22.214.171.124 such ip address, the callp try to route the call to this endpoint, i think that firstly that will take emouth time to replay and it's can genarate an ankown cause to pass to the second endpoint.
03-05-2009 11:18 AM
It only re-orders them at run-time like this if ALL of the endpoints in the route are of type Gateway.
So make sure that the extra endpoint you put in does not have a type of Gateway. "Terminal" type is the best for this workaround.
So yes, put in (with like an order of 9) an endpoint of 126.96.36.199 with type=Terminal and it will then go with the provisioned order always.
03-15-2009 07:33 AM
My config is very simple:
v7122 TYPE GATEWAY PRIORITY 2
VEGASTREAM TYPE GATEWAY PRIORITY 1
if both endpoint are active. the callp route every call to the second endpoint "with priority 2".
if i disable the route for the second endpoint " with priority 2", it route call to the gateway with priority 1.
This message was edited by adiltaleb on 3-15-09 @ 7:39 AM
03-17-2009 08:20 AM
Then put it in as sort order 3 in your route.
The problem is there is a bug where the "last registered" endpoint will take priority over the sort order. This is a bug and has been reported to 3Com for a fix in future builds.
The work around is adding the dumb terminal which will render the registration problem moot and cause sort order to work properly.