[sr-dev] [tracker] Comment added: [selects] @v.branch and others are not exported

sip-router admin at sip-router.org
Thu Jun 30 14:31:00 CEST 2011


THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#138 - [selects] @v.branch and others are not exported
User who did this - Iñaki Baz Castillo (ibc)

----------
The request is correct (no parsing errors at all):

DEBUG: <core> [parser/parse_via.c:1287]: Found param type 232,<branch> = <z9hG4bKaxdawfnv>; state=16

Then when running this xlog:

xlog("L_INFO", "[$sel(@v.branch)] $rm  from $fu ($fU) to $ru ($sel(@v.transport) $si : $sp)");

I get <null> for $sel(@v.branch):

DEBUG: <core> [select_core.c:378]: missing VIA[6] header
DEBUG: <core> [parser/parse_to.c:174]: DEBUG: add_param: tag=wohrg
DEBUG: <core> [parser/parse_to.c:803]: end of header reached, state=29
DEBUG: <core> [select.c:424]: Calling SELECT 0x7f5e99bd9890
INFO: <script>: [<null>] ACK  from sip:test_ibc at aliax.net (test_ibc) to sip:kaka at aliax.net (UDP 192.168.1.16 : 15060)


So, what does it mean "[select_core.c:378]: missing VIA[6] header" ?
It's not missing at all. It's an INVITE from Twinkle, 100% correct:

INVITE sip:kaka at aliax.net SIP/2.0
Via: SIP/2.0/UDP 192.168.1.16:15060;rport;branch=z9hG4bKfzqlmkkf
Max-Forwards: 70
To: <sip:kaka at aliax.net>
From: "OverSIP" <sip:test_ibc at aliax.net>;tag=hkrmz
Call-ID: soilztpqcxyvhfr at ibc-laptop
CSeq: 986 INVITE
Contact: <sip:test_ibc at 192.168.1.16:15060;transport=udp>
Content-Type: application/sdp
Allow: INVITE,ACK,BYE,CANCEL,OPTIONS,PRACK,REFER,NOTIFY,SUBSCRIBE,INFO,MESSAGE
Supported: replaces,norefersub,100rel
User-Agent: Twinkle/1.4.2
Content-Length: 309

[...]
----------

More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=138#comment232

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.



More information about the sr-dev mailing list