[Freeswitch-users] No NOTIFY MWI when registering via proxy.
Michael Jerris
mike at jerris.com
Wed Nov 25 09:39:10 PST 2009
Try an alias on the sip profile.
Mike
On Nov 24, 2009, at 5:56 PM, Peter P GMX wrote:
> Anthony, thanks for the hint,
>
> I receive events like the following
> RECV EVENT
> Event-Name: MESSAGE_WAITING
> Core-UUID: e71632c8-d948-11de-942b-0138c6269e37
> FreeSWITCH-Hostname: sip11.mydomain.com
> FreeSWITCH-IPv4: 192.168.178.200
> FreeSWITCH-IPv6: ::1
> Event-Date-Local: 2009-11-24 23:33:13
> Event-Date-GMT: Tue, 24 Nov 2009 22:33:13 GMT
> Event-Date-Timestamp: 1259101993918617
> Event-Calling-File: mod_voicemail.c
> Event-Calling-Function: update_mwi
> Event-Calling-Line-Number: 1738
> MWI-Messages-Waiting: yes
> MWI-Message-Account: 200 at sip1.mydomain.com
> MWI-Voice-Message: 4/1 (0/0)
>
> I think the problem may be the Freeswitch cluster we are working with.
> All phones register with realm (e.g. 200 at sip1.mydomain.com). The FS
> hostname is sip11.mydomain.com resp. sip12.mydomain.com on the other host.
> With xml_curl we ensure that for both domain names a directory entry is
> passed back. That way it works nicely with registering phones, receiving
> voicemails, recording voicemails etc. but not for MWI. For recording and
> querying voicemails we use the realm instead of the domain name and that
> way it works.
>
> When a voicemail has finished recording - and at the time the above
> message occurs - I see 2 directory xml_curl requests with
> Event-Calling-File=mod_voicemail.c&Event-Calling-Function=resolve_id
> One I expect is for retrieving the MWI data and the other one for
> sending the VM email (which is sucessfully sent).
>
> Any hint how we can workaround this? Or is there a parameter to tell
> mod_voicemail that is should use the realm instead of the local hostname
> for sending MWI?
>
> Best regards
> Peter
>
> Anthony Minessale schrieb:
>> connect to FS with fs_cli
>>
>> Issue the command:
>>
>> /events MESSAGE_QUERY MESSAGE_WAITING
>>
>> then leave some voice mails
>>
>> probably you have a mis-configuration where the user/domain/profile
>> cannot be resolved to the correct
>> sofia profile to send the notify
>>
>> The event starts out as a freeswitch event and is translated into the
>> notify by mod_sofia but only if it can
>> match the event to a real sip user
>>
>>
>>
>>
>> On Tue, Nov 24, 2009 at 2:54 PM, Peter P GMX <Prometheus001 at gmx.net
>> <mailto:Prometheus001 at gmx.net>> wrote:
>>
>> Hello,
>>
>> I have a similar problem with Freeswitch behind OpenSIPS as a load
>> balancer:
>> When registering, Freeeswitch does not send a MWI NOTIFY message for a
>> Phone which has voicemails. Even after recording a new voicemail there
>> is no NOTIFY message sent. And there are no error messages on the
>> console.
>>
>> I have explicitely set
>> <param name="manage-presence" value="true"/> in the internal
>> profile.
>>
>> When a phone is set up I get the following
>> Snom Phone REGISTER => OpenSIPS=> Freeswitch
>> Freeswitch OK => OpenSIPS=>Snom Phone
>>
>> Snom Phone SUBSCRIBE => OpenSIPS=> Freeswitch
>> Freeswitch 202 Accepted => OpenSIPS=>Snom Phone
>>
>> Snom Phone PUBLISH => OpenSIPS=> Freeswitch
>> Freeswitch 200 OK => OpenSIPS=>Snom Phone
>> So presence generally seems to work.
>>
>> But ngrepping the Network traffic there's no MWI NOTIFY message coming
>> from Freeswitch to any phone.
>> FreeSWITCH Version is 1.0.trunk (15648), so the patch discussed before
>> should be already there.
>>
>> Any idea how to force the NOTIFY messages?
>>
>>
>> Best regards
>> Peter
>>
>> Here's the debug Level9 output for nta and nua when a phone with VMs
>> registers, seems like there is no error in it:
>>
>> freeswitch at sip11.mydomain.com
>> <mailto:freeswitch at sip11.mydomain.com>> nta: received REGISTER
>> sip:sip1.mydomain.com <http://sip1.mydomain.com> SIP/2.0 (CSeq 7)
>> nta: REGISTER (7) going to a default leg
>> nua: nua_stack_process_request: entering
>> nua: nh_create: entering
>> nua: nh_create_handle: entering
>> nua: nua_stack_set_params: entering
>> nua(0x7fd5d409c8f0): event i_register 100 Trying
>> nua: nua_application_event: entering
>> nua: nua_respond: entering
>> nua(0x7fd5d409c8f0): sent signal r_respond
>> nua: nua_handle_destroy: entering
>> nua(0x7fd5d409c8f0): sent signal r_destroy
>> nua: nua_handle_magic: entering
>> nua: nua_handle_destroy: entering
>> nua(0x7fd5d409c8f0): recv signal r_respond 401 Unauthorized
>> nua: nua_stack_set_params: entering
>> nta: sent 401 Unauthorized for REGISTER (7)
>> nta: timer set to 32000 ms
>> nua(0x7fd5d409c8f0): recv signal r_destroy
>> nta_leg_destroy((nil))
>> nta: received REGISTER sip:sip1.mydomain.com
>> <http://sip1.mydomain.com> SIP/2.0 (CSeq 6)
>> nta: REGISTER (6) going to a default leg
>> nua: nua_stack_process_request: entering
>> nua: nh_create: entering
>> nua: nh_create_handle: entering
>> nua: nua_stack_set_params: entering
>> nua(0x905a80): event i_register 100 Trying
>> nua: nua_application_event: entering
>> nua: nua_respond: entering
>> nua(0x905a80): sent signal r_respond
>> nua: nua_handle_destroy: entering
>> nua(0x905a80): recv signal r_respond 401 Unauthorized
>> nua(0x905a80): sent signal r_destroy
>> nua: nua_stack_set_params: entering
>> nua: nua_handle_magic: entering
>> nua: nua_handle_destroy: entering
>> nta: sent 401 Unauthorized for REGISTER (6)
>> nua(0x905a80): recv signal r_destroy
>> nta_leg_destroy((nil))
>> nta: received PUBLISH sip:100 at sip1.mydomain.com
>> <mailto:sip%3A100 at sip1.mydomain.com> SIP/2.0 (CSeq 3)
>> nta: PUBLISH (3) going to a default leg
>> nua: nua_stack_process_request: entering
>> nua: nh_create: entering
>> nua: nh_create_handle: entering
>> nua: nua_stack_set_params: entering
>> nua(0x905f10): event i_publish 100 Trying
>> nua: nua_application_event: entering
>> nua: nua_respond: entering
>> nua(0x905f10): sent signal r_respond
>> nua: nua_handle_magic: entering
>> nua: nua_handle_destroy: entering
>> nua(0x905f10): recv signal r_respond 200 OK
>> nua: nua_stack_set_params: entering
>> nua(0x905f10): sent signal r_destroy
>> nta: sent 200 OK for PUBLISH (3)
>> nua(0x905f10): recv signal r_destroy
>> nta_leg_destroy((nil))
>> nta: received SUBSCRIBE sip:mod_sofia at 192.168.178.200:5062
>> <http://sip:mod_sofia@192.168.178.200:5062> SIP/2.0 (CSeq 2)
>> nta: canonizing sip:mod_sofia at 192.168.178.200:5062
>> <http://sip:mod_sofia@192.168.178.200:5062> with contact
>> nta: SUBSCRIBE (2) going to existing leg
>> nua: nua_stack_process_request: entering
>> nta: sent 200 OK for SUBSCRIBE (2)
>> nua(0x905560): event i_subscribe 200 OK
>> nua: nua_application_event: entering
>> nta: received REGISTER sip:sip1.mydomain.com
>> <http://sip1.mydomain.com> SIP/2.0 (CSeq 8)
>> nta: REGISTER (8) going to a default leg
>> nua: nua_stack_process_request: entering
>> nua: nh_create: entering
>> nua: nh_create_handle: entering
>> nua: nua_stack_set_params: entering
>> nua(0x7fd5dc073ba0): event i_register 100 Trying
>> nua: nua_application_event: entering
>> nua: nua_respond: entering
>> nua(0x7fd5dc073ba0): sent signal r_respond
>> nua(0x7fd5dc073ba0): recv signal r_respond 200 OK
>> nua: nua_stack_set_params: entering
>> nua: nua_handle_destroy: entering
>> nua(0x7fd5dc073ba0): sent signal r_destroy
>> nua: nua_handle_magic: entering
>> nua: nua_handle_destroy: entering
>> nta: sent 200 OK for REGISTER (8)
>> nua(0x7fd5dc073ba0): recv signal r_destroy
>> nta_leg_destroy((nil))
>> nta: received REGISTER sip:sip1.mydomain.com
>> <http://sip1.mydomain.com> SIP/2.0 (CSeq 7)
>> nta: REGISTER (7) going to a default leg
>> nua: nua_stack_process_request: entering
>> nua: nh_create: entering
>> nua: nh_create_handle: entering
>> nua: nua_stack_set_params: entering
>> nua(0x8fc3d0): event i_register 100 Trying
>> nua: nua_application_event: entering
>> nua: nua_respond: entering
>> nua(0x8fc3d0): sent signal r_respond
>> nua(0x8fc3d0): recv signal r_respond 200 OK
>> nua: nua_handle_destroy: entering
>> nua: nua_stack_set_params: entering
>> nua(0x8fc3d0): sent signal r_destroy
>> nua: nua_handle_magic: entering
>> nua: nua_handle_destroy: entering
>> nta: sent 200 OK for REGISTER (7)
>> nua(0x8fc3d0): recv signal r_destroy
>> nta_leg_destroy((nil))
>> nta: received SUBSCRIBE sip:100 at sip1.mydomain.com
>> <mailto:sip%3A100 at sip1.mydomain.com>;user=phone SIP/2.0
>> (CSeq 1)
>> nta: SUBSCRIBE (1) going to a default leg
>> nua: nua_stack_process_request: entering
>> nua: nh_create: entering
>> nua: nh_create_handle: entering
>> nua: nua_stack_set_params: entering
>> nta_leg_tcreate(0x7fd5dc03add0)
>> nua(0x7fd5dc078b70): adding notify usage with event message-summary
>> nua(0x7fd5dc078b70): event i_subscribe 100 Trying
>> nua: nua_application_event: entering
>> nua(): refresh notify after 3600 seconds (in [3600..3600])
>> nua: nua_respond: entering
>> nua(0x7fd5dc078b70): sent signal r_respond
>> nua(0x7fd5dc078b70): recv signal r_respond 202 Accepted
>> nua: nua_stack_set_params: entering
>> nta: sent 202 Accepted for SUBSCRIBE (1)
>>
>>
>>
>>
>>
>> mayamatakeshi schrieb:
>>>
>>> On 9/12/09, *mayamatakeshi* <mayamatakeshi at gmail.com
>> <mailto:mayamatakeshi at gmail.com>
>>> <mailto:mayamatakeshi at gmail.com
>> <mailto:mayamatakeshi at gmail.com>>> wrote:
>>>
>>>
>>> On Sat, Sep 12, 2009 at 1:45 AM, Michael Jerris
>> <mike at jerris.com <mailto:mike at jerris.com>
>>> <mailto:mike at jerris.com <mailto:mike at jerris.com>>> wrote:
>>>
>>> Following up, did a bug get created for this issue?
>>>
>>>
>>> Hello,
>>> yes.
>>> http://jira.freeswitch.org/browse/MODSOFIA-26
>>>
>>>
>>> Just to simplify things in case someone searches the list:
>>> Issue was solved on rev 14851.
>>> Thank you all.
>>>
>> ------------------------------------------------------------------------
>>>
>>> _______________________________________________
>>> FreeSWITCH-users mailing list
>>> FreeSWITCH-users at lists.freeswitch.org
>> <mailto: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
>>>
>>
>> _______________________________________________
>> FreeSWITCH-users mailing list
>> FreeSWITCH-users at lists.freeswitch.org
>> <mailto: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
>>
>>
>>
>>
>> --
>> Anthony Minessale II
>>
>> FreeSWITCH http://www.freeswitch.org/
>> ClueCon http://www.cluecon.com/
>> Twitter: http://twitter.com/FreeSWITCH_wire
>>
>> AIM: anthm
>> MSN:anthony_minessale at hotmail.com
>> <mailto:MSN%3Aanthony_minessale at hotmail.com>
>> GTALK/JABBER/PAYPAL:anthony.minessale at gmail.com
>> <mailto:PAYPAL%3Aanthony.minessale at gmail.com>
>> IRC: irc.freenode.net <http://irc.freenode.net> #freeswitch
>>
>> FreeSWITCH Developer Conference
>> sip:888 at conference.freeswitch.org
>> <mailto:sip%3A888 at conference.freeswitch.org>
>> iax:guest at conference.freeswitch.org/888
>> <http://iax:guest@conference.freeswitch.org/888>
>> googletalk:conf+888 at conference.freeswitch.org
>> <mailto:googletalk%3Aconf%2B888 at conference.freeswitch.org>
>> pstn:213-799-1400
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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
>>
>
> _______________________________________________
> 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
More information about the FreeSWITCH-users
mailing list