Why is loopback required to originate from endpoints registered on multiple profiles?
Hi, Is it part of the implementation of sofia that means, even with a shared reg and presence db, that if I have the same extension registered on both the default profile and a NAT profile, that originate user/1000 <destno> seems to only ring one of the registered endpoints (and it seems so far random which one rings), while originate loopback/1000 <destno> and for an existing call bridge user/1000 happily rings both endpoints? Cheers Alex
What does your dial-string and logs look like for that originate? -- Brian West brian@freeswitch.org Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED) On Apr 29, 2014, at 12:33 PM, Alex Crow <acrow@integrafin.co.uk> wrote:
Hi,
Is it part of the implementation of sofia that means, even with a shared reg and presence db, that if I have the same extension registered on both the default profile and a NAT profile, that
originate user/1000 <destno>
seems to only ring one of the registered endpoints (and it seems so far random which one rings), while
originate loopback/1000 <destno>
and for an existing call
bridge user/1000
happily rings both endpoints?
Cheers
Alex
Hi Brian, Which one? The one that doesn't work? If so, I'm not sure what you mean by "dial-string". Unless you're talking about the <destno> bit (which seems not to matter at all, it's just the originator part that is the problem). I've tested so far with <destno> as an extension on the local machine and as one on a remote server (Mitel and another FS box) and it's the same on both. The <destno>s are all referenced in the dialplan. eg originate user/1000 1234 XML default and originate user/1000 117399 XML default both exhibit the problem, where 1234 is a local extension on the same FS instance and 117399 is routed through a gateway. Those two destinations ring OK once the endpoint that has been ringing on "1000" has picked up, it's just that I have 2 endpoints registered as "1000@domain" and only one of them rings when the originate starts if I user the user/1000 syntax. Using loopback makes all registered extensions "1000@domain" ring for the A leg (if that's the right term to use for that). Cheers Alex On 29/04/14 20:06, Brian West wrote:
What does your dial-string and logs look like for that originate? -- Brian West brian@freeswitch.org <mailto:brian@freeswitch.org>
Twitter: @FreeSWITCH , @briankwest http://www.freeswitchbook.com http://www.freeswitchcookbook.com
T: +1.918.420.9001 | F: +1.918.420.9002 | M: +1.918.424.WEST iNUM: +883 5100 1420 9001 ISN: 410*543 Skype:briankwest PGP Key: http://www.bkw.org/key.txt (AB93356707C76CED)
On Apr 29, 2014, at 12:33 PM, Alex Crow <acrow@integrafin.co.uk <mailto:acrow@integrafin.co.uk>> wrote:
Hi,
Is it part of the implementation of sofia that means, even with a shared reg and presence db, that if I have the same extension registered on both the default profile and a NAT profile, that
originate user/1000 <destno>
seems to only ring one of the registered endpoints (and it seems so far random which one rings), while
originate loopback/1000 <destno>
and for an existing call
bridge user/1000
happily rings both endpoints?
Cheers
Alex
_________________________________________________________________________ Professional FreeSWITCH Consulting Services: consulting@freeswitch.org http://www.freeswitchsolutions.com
FreeSWITCH-powered IP PBX: The CudaTel Communication Server http://www.cudatel.com
Official FreeSWITCH Sites http://www.freeswitch.org http://wiki.freeswitch.org http://www.cluecon.com
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (2)
-
Alex Crow
-
Brian West