Hi Andreas, Hi Bradley,
Couple of days ago there were some fixes for maddr usage in VIA header (
affecting nat detection, reply routing, etc). There is some more work to
do for maddr in R-URI, but I hope it will be soon.
Regards,
Bogdan
Andreas Granig wrote:
Bradley,
I've submitted
http://sourceforge.net/tracker/index.php?func=detail&aid=1660338&gr…
some time ago, and the UA in question is also a Nortel CS2K, so it
seems like this UA is using maddr in multiple places. Maybe the
overall maddr-handling in OpenSER has to be reviewed (I'm not sure if
your case complies with RFC 3261 and thus is valid though).
Cheers,
Andreas
Watkins, Bradley wrote:
I'm using OpenSER to connect to a Nortel
CS1000M, and I'm having some
problems.
The way the Nortel works is that it has what they call a Network Routing
Service (redirect server, really), that issues either a 302 (if a single
SIP gateway exists on the CS1000) or a 300 (if multiple).
Here's a sample 300 from my system (IPs and domains changed to protect
the guilty):
U 10.1.1.3:5060 -> 10.0.1.1:5060
SIP/2.0 300 Multiple Choices.
Via: SIP/2.0/UDP
10.0.1.1;branch=z9hG4bKa66e.99fc1a25.1;received=10.0.1.1.
Via: SIP/2.0/UDP 10.1.3.114;branch=z9hG4bK7d42804867A25509.
From: "0004f2145263"
<sip:0004f2145263@dtw-openser01.sub.domain.com>;tag=5F7CDD45-DDCE1F92.
To: <sip:12345@dtw-openser01.sub.domain.com;user=phone>;tag=34887.
Call-ID: 58dd5646-e86d140f-c2ead634(a)10.1.3.114.
CSeq: 1 INVITE.
Contact:
<sip:12345;phone-context=udp@domain.com:5060;maddr=10.1.1.1;transport=ud
p;x-nt-redirect=redirect-server;x-nt-redirect=redirect-server>.
Contact:
<sip:12345;phone-context=udp@domain.com:5060;maddr=10.1.1.2;transport=tc
p;x-nt-redirect=redirect-server;x-nt-redirect=redirect-server>.
Content-Length: 0.
The problem I have is that the Contacts have an maddr, and I need relay
to it. However, I can't seem to be able to use transformations to get
the maddr for relaying. Here are some log messages with comments
inline:
Jul 16 19:50:49 dtw-openser01 /usr/local/sbin/openser[4306]: Branches
are:
<sip:12345;phone-context=udp@domain.com:5060;maddr=10.1.1.1;transport=ud
p;x-nt-redirect=redirect-server>;q=0.01
This is just an xlog of $bR, but I'm not sure where the q= value is
coming from (get_redirects?).
Jul 16 19:50:49 dtw-openser01 /usr/local/sbin/openser[4306]: ERROR:
parse_uri: bad uri, state 0 parsed: <<sip> (4) /
<<sip:12345;phone-context=udp@domain.com:5060;maddr=10.1.1.1;transport=u
dp;x-nt-redirect=redirect-server>;q=0.01> (120)
Jul 16 19:50:49 dtw-openser01 /usr/local/sbin/openser[4306]:
tr_eval_uri: invalid uri
[<sip:12345;phone-context=udp@domain.com:5060;maddr=10.1.1.1;transport=u
dp;x-nt-redirect=redirect-server>;q=0.01]
These are what I get as a result of trying to xlog $(bR{uri.maddr})
Anyway, I would be greatly appreciative of any help someone might offer
on the matter.
Regards,
- Brad
The contents of this e-mail are intended for the named addressee
only. It contains information that may be confidential. Unless you
are the named addressee or an authorized designee, you may not copy
or use it, or disclose it to anyone else. If you received it in error
please notify us immediately and then destroy it.
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users