Topic: Trying to route calls from one sail to another

[Franco]

Hi S,
I have two boxes setup, but only one has a TDM card on it.
So I´m trying to route these calls from one to another, both in and out.
I have set the siblings unpriviledged and tested using softphones, the calls get routed correctly when I dial from one box to another.
Now to the trunklines, I´m getting this error
On the fist box where the TDM card is (172.16.0.3):

Code: [Select]

AGI Rx << EXEC Dial IAX2/hp~v4@v4~hp/DAHDI1-1||
[Jul 17 23:30:37] WARNING[4394]: chan_iax2.c:8067 socket_process: Call rejected by 172.16.0.1: No such context/    extension
And on the second box where I´m routing the calls, no TDM (172.16.0.1)

Code: [Select]

[Jul 17 23:51:18] NOTICE[5359]: chan_iax2.c:8160 socket_process: Rejected connect attempt from 172.16.0.3, request 'DAHDI1-1@internal' does not exist

Any help is appreciated.

[David Harper]

Just to confirm, you are using a SAIL to SAIL trunk to link the two servers?

[Franco]

yes

[David Harper]

What  versions of Sail are you running on the two servers?

[Franco]

Hi,
I'm running sail-2.2.1-759 on the server without TDM (zaptel) and sail-2.3.1-20 on the server with the TDM, hence I'm using DAHDI.

[David Harper]

I'm no expert, but from the logs it looks like DAHDI on the TDM box is trying to talk to DAHDI on the standalone box.

[SARK devs]

Hi Franco,

Failrly complex issue and not easy to answer succinctly but I'll try.   Analogue calls have no number associated with them, just a channel number, e.g. DAHDI/1, DAHDI/2 and so on. SARK/SAIL routing is number (or character string) based.   When an analogue call arrives, SAIL allocates a number string to it.  Essentially this is the channel name (DAHDI/1-1) but with the slash(/) removed (DAHDI1-1).  Now, you want to ship the call over IAX to another machine.  It will be sent with a DNID of DAHDI1-1 or DAHDI1-2, etc.  However, unless you have a dailplan entry of DAHDI1-1 in the receiving machine then your call will be rejected. 

This is exactly what is happening...

Code: [Select]

Dial IAX2/hp~v4@v4~hp/DAHDI1-1||

Code: [Select]

...Call rejected by 172.16.0.1: No such context/extension
The receiving SAIL box doesn't know what to do with the call, so it rejects it. 

In SAIL-2.3.2-3 there is a cure for this problem by using something called a DiD-Class.  DiD-Class exists in 2.3.1-20 but it doesn't work properly.

2.3.2-3 will be released in a few days so you should not have too long to wait for this fix.

Alternatively, you can just create a custom app along the lines of

Code: [Select]

exten=>DAHDI1-1,1,Dial(some extension)

Apologies for the problem but, to our knowledge, no one has ever wanted to cross-dock analogue calls.  Cross docking between machines is ususally only done by customers with ISDN30 digital circuits or SIP trunks, both of which work just fine.


Best

S   

[Franco]

Thanks S,
It's what I endend it up doing, created a custom app:

Code: [Select]

exten=>s,1,Dial(IAX2/v4~hp/7130)
exten=>s,2,HangupI'll give a try on yours to see how it goes, and wait for the new release.

Thanks a lot.