[ previous ] [ next ] [ threads ]
 To :  yate@v...
 From :  Alexey Loshkarev <elf2001@g...>
 Subject :  multiple devices sharing one extension number
 Date :  Sun, 17 Mar 2013 19:14:02 +0200
Hello.

Can multiple SIP-clients have one extension with Yate?
I'm using self-written yate backend in our company.

Sometimes, we need to have different devices (for example, hard-phones and
soft-phones) to have same extension number.
Now we are resolved it with call queue (fork to two devices) and
replacement of callto-name at call from this devices, but this method looks
ugly.

Example:
When you call, for example, to
100, call forked to 101 and 102.
And then call back from 101 to 200, subscriber at 200 sees me as 100 and
can call back to this number.


I'm trying to route call to several extensions but with no success.

My backend handle multiple registrations from same extension without any
problem, but return that locations to call.route is problematically.

call.route message must receive a response - target and optional params
(required for tcp/tls connection). But this is data for only one extension.
Basic documentation says similar - only one location per one route.

"fork" method can target call to different extensions at once, but not to
one extension at different hosts/ports (ok, this can work with UDP, but not
with TCP/TLS, as I can't return additional parameters for each target).

Is there any other method?



-- 
----------------
Best regards
Alexey Loshkarev
mailto:elf2001@g...



Hello.

Can multiple SIP-clients have one extension with Yate?
I'm using self-written yate backend in our company.

Sometimes, we need to have different devices (for example, hard-phones and soft-phones) to have same extension number. 
Now we are resolved it with call queue (fork to two devices) and replacement of callto-name at call from this devices, but this method looks ugly.

Example:
When you call, for example, to
100, call forked to 101 and 102.
And then call back from 101 to 200, subscriber at 200 sees me as 100 and can call back to this number.


I'm trying to route call to several extensions but with no success.

My backend handle multiple registrations from same extension without any problem, but return that locations to call.route is problematically.

call.route message must receive a response - target and optional params (required for tcp/tls connection). But this is data for only one extension. 
Basic documentation says similar - only one location per one route.

"fork" method can target call to different extensions at once, but not to one extension at different hosts/ports (ok, this can work with UDP, but not with TCP/TLS, as I can't return additional parameters for each target).

Is there any other method?



--
----------------
Best regards
Alexey Loshkarev
mailto:elf2001@g...