[OpenSIPS-Users] Double via in MI generated NOTIFY

Stas Kobzar stas.kobzar at modulis.ca
Mon Jun 1 16:42:17 CEST 2015


I am sending NOTIFY packet with event "check-sync" to reload phone

I am doing it with opensips FIFO mi.

My command looks like this:
opensipsctl fifo t_uac_dlg NOTIFY sip:7037 at . . '"From: <
sip:7037 at voip.etsmtl.ca>;tag=8755a8d01aa27e903a6f4ccaf393f04\r\nTo: <
sip:7037 at voip.etsmtl.ca>\r\nEvent: check-sync\r\n"'

When I use IP address in RURI (sip:7037 at it works as expected.

However, when I use domain name in RURI (like this:
sip:7037 at campus.voip.etsmtl.ca) and my command looks like this:
opensipsctl fifo t_uac_dlg NOTIFY sip:7037 at campus.voip.etsmtl.ca . .
'"From: <sip:7037 at voip.etsmtl.ca>;tag=8755a8d01aa27e903a6f4ccaf393f04\r\nTo:
<sip:7037 at voip.etsmtl.ca>\r\nEvent: check-sync\r\n"'

I have two Via headers in my resulting NOTIFY packet with different branche

NOTIFY sip:7037 at SIP/2.0.
Via: SIP/2.0/UDP;branch=z9hG4bK0872.598957f2.0.
Via: SIP/2.0/UDP;branch=z9hG4bK0872.498957f2.0.
To: sip:7037 at campus.voip.etsmtl.ca.
From: <sip:7037 at campus.voip.etsmtl.ca>;tag=734c62bd59eb9f33d3e6313898450dd1.
CSeq: 10 NOTIFY.
Call-ID: 693206c572f70ff6-19332 at
Max-Forwards: 69.
Content-Length: 0.
Server: ETS voip router01.
Event: check-sync

In first case, I do not even see the packet in main route but I see it in

In my second case I see it in main route but the packet is sent with double
Via header.

I am sure it is not my routing script, because I have just put a forward to
some IP whenever NOTIFY is received and I still have this problem.

Is it a known issue?

Everything still works fine, but having a double Via in logs a bit

Thank you,

Stas Kobzar

Developeur VoIP / VoIP Developer


Modulis­.ca Inc.

# Bureau / Office: 514-284-2020 x 246

Email: s <http://firstname.lastname>tas.kobzar at modulis.ca


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20150601/0f001950/attachment.htm>

More information about the Users mailing list