[Freeswitch-users] USER_NOT_REGISTERED when freeswtch is registered at another freeswitch.

Fri Sep 28 12:17:24 MSD 2012

Hello Lawrence,

I set the

  <param name="extension-in-contact" value="true"/>

to the gateway definition and now the registration string in
sip_registarations looks much better:
   "user"<sip:400 at 10.8.0.42:5080;transport=udp;gw=sip1.mydomain.com>

However with sofia_contact I still have the same problem:
  freeswitch at internal> sofia_contact 400
  error/user_not_registered
  freeswitch at internal> sofia_contact */400

sofia/internalvpn/sip:400 at 10.8.0.42:5080;transport=udp;gw=sip1.mydomain.com

But still the same when dialling:
EXECUTE sofia/internal/200 at sip1.mydomain.com
bridge({sip_invite_domain=sip1.mydomain.com}user/400 at sip1.mydomain.com)
2012-09-28 10:07:29.089083 [DEBUG] switch_channel.c:1062
sofia/internal/200 at sip1.mydomain.com EXPORTING[export_vars]
[dialed_ext]=[400] to event
2012-09-28 10:07:29.089083 [DEBUG] switch_ivr_originate.c:1961 Parsing
global variables
2012-09-28 10:07:29.089083 [DEBUG] switch_event.c:1478 Parsing variable
[sip_invite_domain]=[sip1.mydomain.com]
2012-09-28 10:07:29.189083 [DEBUG] switch_channel.c:1062
sofia/internal/200 at sip1.mydomain.com EXPORTING[export_vars]
[dialed_ext]=[400] to event
2012-09-28 10:07:29.189083 [DEBUG] switch_ivr_originate.c:1961 Parsing
global variables
2012-09-28 10:07:29.189083 [DEBUG] switch_event.c:1478 Parsing variable
[presence_id]=[400 at sip1.mydomain.com]
2012-09-28 10:07:29.189083 [DEBUG] switch_event.c:1478 Parsing variable
[transfer_fallback_extension]=[400]
2012-09-28 10:07:29.189083 [NOTICE] switch_ivr_originate.c:2544 Cannot
create outgoing channel of type [error] cause: [USER_NOT_REGISTERED]

Best regards
Peter

On 09/28/12 00:11, Lawrence Conroy wrote:
> Hi there,
>  in addition, to have the VPN'd fS (box2) show up as extension 400 in the box1 fS, goto
> the gateway definition (on box2) and make sure that <param name="extension" value="400"/>
> and <param name="extension-in-contact" value="true"/> are set.
> For extra points, look in the wiki for "auto_to_user".
>
> I'm also curious about the results of sofia_contact */400
> (probably for the same reason ;).
>
> all the best,
>   Lawrence
>
> On 27 Sep 2012, at 22:47, Michael Collins wrote:
>> Just for kicks, try this:
>>
>> sofia_contact */400
>>
>> I'm curious about something.
>> -MC
>>
>> On Thu, Sep 27, 2012 at 2:24 PM, Peter Steinbach <lists at telefaks.de> wrote:
>>
>>> Hello,
>>>
>>> I have 2 Freeswitch boxes.
>>> Box 2 is registering as number 400 via VPN to box 1 (like a regular
>>> phone). I can see in the sip_registrations database that the phone is
>>> registered. And Box2 shows "
>>>   vpn::sip1.mydomain.com       gateway
>>> sip:400 at 10.8.0.1:5075      REGED
>>> So at the first glance everything seems ok.
>>>
>>> However in my vpn profile
>>>   sofia status profile internalvpn
>>> the Freeswitch box2 is not shown as a registration entry.
>>>
>>> I think this is the reason why we receive the following when we try to
>>> call the box 2 (number 400):
>>> EXECUTE sofia/internal/200 at sip1.mydomain.com
>>> bridge({sip_invite_domain=sip1.mydomain.com}user/400 at sip1.mydomain.com)
>>> 2012-09-27 23:09:58.149196 [DEBUG] switch_channel.c:1062
>>> sofia/internal/200 at sip1.mydomain.com EXPORTING[export_vars]
>>> [dialed_ext]=[400] to event
>>> 2012-09-27 23:09:58.149196 [DEBUG] switch_ivr_originate.c:1961 Parsing
>>> global variables
>>> 2012-09-27 23:09:58.149196 [DEBUG] switch_event.c:1478 Parsing variable
>>> [sip_invite_domain]=[sip1.mydomain.com]
>>> 2012-09-27 23:09:58.169252 [DEBUG] switch_core_session.c:924 Send signal
>>> sofia/internal/200 at sip1.mydomain.com [BREAK]
>>> 2012-09-27 23:09:58.269299 [DEBUG] switch_channel.c:1062
>>> sofia/internal/200 at sip1.mydomain.com EXPORTING[export_vars]
>>> [dialed_ext]=[400] to event
>>> 2012-09-27 23:09:58.269299 [DEBUG] switch_ivr_originate.c:1961 Parsing
>>> global variables
>>> 2012-09-27 23:09:58.269299 [DEBUG] switch_event.c:1478 Parsing variable
>>> [presence_id]=[400 at sip1.mydomain.com]
>>> 2012-09-27 23:09:58.269299 [DEBUG] switch_event.c:1478 Parsing variable
>>> [transfer_fallback_extension]=[400]
>>> 2012-09-27 23:09:58.269299 [DEBUG] sofia.c:6040 Channel
>>> sofia/internal/200 at sip1.mydomain.com entering state [early][180]
>>> 2012-09-27 23:09:58.269299 [NOTICE] switch_ivr_originate.c:2544 Cannot
>>> create outgoing channel of type [error] cause: [USER_NOT_REGISTERED]
>>>
>>>
>>> freeswitch at internal> sofia_contact 400
>>> error/user_not_registered
>>> freeswitch at internal> sofia_contact 200
>>> sofia/internal/sip:200 at 192.168.178.105:2048
>>> ;line=1vz0u23u;fs_nat=yes;fs_path=sip%3A200%40217.24.xx.xxx%3A20393%3Bline%3D1vz0u23u
>>> So 200 seems ok, 400 not.
>>>
>>> When I look at the contact field in the sip_registrations table, I see
>>> "user"<sip:gw+sip1.mydomain.com at 10.8.0.42:5080;transport=udp;gw=
>>> sip1.mydomain.com>
>>> so this does not reflect the number 400.
>>>
>>> Here is my gateway config from box2 which registers at box1
>>> (sip1.mydomain.com)
>>> # cat sip1.xml
>>> <include>
>>>  <gateway name="sip1.mydomain.com">
>>>    <param name="from-domain" value="sip1.mydomain.com"/>
>>>    <param name="username" value="400"/>
>>>    <param name="from-user" value="400"/>
>>>    <param name="extension" value="400"/>
>>>    <param name="realm" value="sip1.mydomain.com"/>
>>>    <!-- 5075 registers to the internal VPN profile -->
>>>    <param name="proxy" value="10.8.0.1:5075"/>
>>>    <param name="password" value="xxxxxxxx"/>
>>>    <param name="expire-seconds" value="3600"/>
>>>    <param name="register" value="true"/>
>>>    <param name="register-transport" value="udp"/>
>>>    <param name="retry-seconds" value="20"/>
>>>    <param name="caller-id-in-from" value="true"/>
>>>  </gateway>
>>> </include>
>>>
>>>
>>> My question is: How can I change the gateway definition, so that box2
>>> shows up as a regular registration with number 400? Or am I missing
>>> something different?
>>>
>>> --
>>> With kind regards
>>> Peter Steinbach
>>>
>>> Telefaks Services GmbH
>>> mailto:lists (att) telefaks.de
>>> Internet: www.telefaks.de
>>>
>>>
>>>
>> _________________________________________________________________________
>> Professional FreeSWITCH Consulting Services:
>> consulting at freeswitch.org
>> http://www.freeswitchsolutions.com
>>
>> 
>> 
>>
>> Official FreeSWITCH Sites
>> http://www.freeswitch.org
>> http://wiki.freeswitch.org
>> http://www.cluecon.com
>>
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
>> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
>> http://www.freeswitch.org
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> 
> 
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://wiki.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>

-- 
With kind regards
Peter Steinbach 

Telefaks Services GmbH
mailto:lists (att) telefaks.de
Internet: www.telefaks.de