trunk to other system and route policy issue

Status
Not open for further replies.

witekprytek

Joined
Dec 19, 2007
Messages
145
Reaction score
0
Hi all;
I really don't know where to post this issue (freepbx or asterisk) so I decide post it here. If somebody don't feel comfortable with this subject I will move this to another section (suggestion are welcomed).

I have two systems connected via sip trunk. 1. is Elastix 2.02 and the second is Cisco Call manager 8.x

All functions work fine, I can make calls between both systems.

Some users from CUCM have migrated to asterisk, but they need to be accessible on the old number in CUCM - so they have simply "forward all" active ith target number on asterisk.
All calls from pstn, trunks or other CUCM users are forwarded to the asterisk extension and everything is fine.
When any asterisk extension try to reach the CUCM number and call is being forwarded back to the elastix (asterisk) - asterisk see the invite with his own extension from trunk - send auth request and do not get response, so simply send the unauthorized 401 SIP message and CUCM drops connection.

I have insecure=invite,port on trunk set on the trunk but it does not helps.

The question is - what variable should be set on the trunk to get connection in the scenario described above.

I know all the numbers on the second system, so my idea is to tell the asterisk that calls for some external numbers should not be forwarded to the trunk but directly to the specified extension. (I have to forward all numbers 8XX to the trunk but some of them are returned back to the asterisk to 58XX extension)

Does anybody have idea how to do such a translations/routing rules on the elastix/asterisk/freepbx?
 
sounds like a tough one, maybe there is a way to do that effectively

another alternative would be to put a message on the cisco system extensions on how to correctly dial the elastix system rather than forwarding the calls for internal extensions and correctly route the inbound calls to the elastix

I am sure someone will be more helpful than my suggestion if you want to alter the normal authentication.

any one have an idea for him
 
I have made some test with "virtual extension"
I have made on the elastix system an virtual extension and have set CF for this extension to the extension which I want to reach.

The effect is that calling from elastix to the short CUCM number, the astsrisk sees this number as his own and do not send the call over the trunk.

This is not very elegant but seems to works fine.

Any better ideas are welcome.
 
Status
Not open for further replies.

Members Online Now

Forum statistics

Threads
111,860
Messages
589,437
Members
164,700
Latest member
Apollo Cloud