[Kamailio-Users] What is wrong with this NOTIFY packet

[Iñaki Baz Castillo]

2010/2/15 Alex Hermann <alex at speakup.nl>:
> On Monday 15 February 2010 09:25:41 Asterisk User wrote:
>> Now to implement MWI i send NOTIFY packet from Asterisk to Kamailio and
>>  from kamailio to SIP extension (Grandstream GXP2000).
>> here is the packet that travels from kamailio to extension and the response
>> sent from extension to kamilio.
>> ===========================
>> NOTIFY sip:1111111 at arzoo.com <sip%3A1111111 at arzoo.com> SIP/2.0
>> Max-Forwards: 10
>> Record-Route: <sip:172.18.100.74;lr;nat=yes>
>> Via: SIP/2.0/UDP 172.18.100.74;branch=z9hG4bK3c3.e1003f03.0
>> Via: SIP/2.0/UDP 127.0.0.1:45382
>> ;received=172.18.100.73;branch=z9hG4bK.4f83530d;rport=45382;alias
>> Via: SIP/2.0/UDP 172.18.100.73:5060
>> From: <sip:111 at arzoo.com <sip%3A111 at arzoo.com>>
>> To: <sip:1111111 at arzoo.com <sip%3A1111111 at arzoo.com>>
>
> NOTIFY's are in-dialog requests. Your From and To header are missing the
> required tags (and look a bit suspicious by themselves too because of the
> double <>).

There is no double <> in the original post. But some mailclients
corrupt a SIP URI appearing into a mail by splitting it into a display
name and mail URI :(





-- 
Iñaki Baz Castillo
<ibc at aliax.net>