[ previous ] [ next ] [ threads ]
 To :  Sven <svoop@d...>, yate@v...
 From :  Gerrit Jacobsen <g_jacobsen@y...>
 Subject :  Re: [yate] Re: Enforce iLBC Codec
 Date :  Fri, 9 Apr 2010 05:10:37 +0000 (GMT)
Sven,

yes routing with registered clients works without regexroute. However you must watch which module has the higher priority. The module with highest priority tries to route first. If that fails the module with the next priority routes.

In your case regexroutes routes first. also you should not route to localhost, that is yate itself. The call then loops.

In theory you can disable regexroute in yate.conf if you just want to route between registered clients. However I believe you want to route to some provider. In that case define the provider in accfile and specify the route to the provider in regexroute.

Cheers.

Gerry







----- Original Message ----
From: Sven 
To: yate@v...
Sent: Thu, 8 April, 2010 23:06:07
Subject: [yate] Re: Enforce iLBC Codec

Hi Gerry

> leave the line
> ${rtp_forward}possible=;rtp_forward=yes
> away. If you want to transcode then rtp must pass through yate.

I see. However, I figured what I set in regexroutes doesn't apply in the first
place, because I called from one SIP phone to another and it's thus routed
directly by regfile.

Adding formats= to the clients in regfile doesn't seem to alter behavior. Do I
have to route these "internal" calls with regexroutes in order to enforce ilbc
for calls between these "internal" clients as well?

I've tried the following, but I get a 483 too many hops:

REGFILE

[general]
route=200

[10]
password=xxx

[20]
password=xxx


REGEXROUTES

[priorities]
preroute=100
route=100

[contexts]
^..$=internal

[internal]
.*=sip/sip:@localhost

Cheers, -sven