(SER 0.8.99-dev19 openbsd/sparc w/local patches) Greetings:
We have rarely received INVITES from UAs not registered on our SER host (from the outside) but as I am setting up a means for a Internet users from foreign realms to listen to audio by making a call to a UA on our network it is now necessary to process foreign INVITES.
Some years ago, this worked as I have logs of successful foreign calls and I have not changed ser.cfg substantially since then, however now I have this problem:
06/17/07 02:13:34 8(3695) ERROR: parse_uri: bad char '@' in state 5 parsed: sip:9202@cybertheque.org (24) / sip:9202@cybertheque.org@10.0.2.200:5060 (40) 06/17/07 02:13:35 8(3695) extract_aor(): Error while parsing Address of Record 06/17/07 02:13:35 8(3695) lookup(): Error while extracting address of record
The foreign caller is dialing SIP:9202@cybertheque.org; cybertheque.org is one of our aliases -- it is the external domain. The internal alias is 'cybertheque.net'; a UA on internal networks simply would dial '9202'. The UA receiving the INVITE is on an internal host with address 10.0.2.200.
I could try 'replace_all("@cybertheque.org","");' but I would like some advice as to the nature of the problem as well. I would also need some test calls from the outside to debug the changes. Anyone willing to call a few times (and let me know before you do so I can make the changes to ser.cfg)?
Thanks,
Michael
Well, sip:9202@cybertheque.org@10.0.2.200:5060 is obviously an invalid aor. Try to figure out where it comes from. g-)
Michael Grigoni wrote:
(SER 0.8.99-dev19 openbsd/sparc w/local patches) Greetings:
We have rarely received INVITES from UAs not registered on our SER host (from the outside) but as I am setting up a means for a Internet users from foreign realms to listen to audio by making a call to a UA on our network it is now necessary to process foreign INVITES.
Some years ago, this worked as I have logs of successful foreign calls and I have not changed ser.cfg substantially since then, however now I have this problem:
06/17/07 02:13:34 8(3695) ERROR: parse_uri: bad char '@' in state 5 parsed: sip:9202@cybertheque.org (24) / sip:9202@cybertheque.org@10.0.2.200:5060 (40) 06/17/07 02:13:35 8(3695) extract_aor(): Error while parsing Address of Record 06/17/07 02:13:35 8(3695) lookup(): Error while extracting address of record
The foreign caller is dialing SIP:9202@cybertheque.org; cybertheque.org is one of our aliases -- it is the external domain. The internal alias is 'cybertheque.net'; a UA on internal networks simply would dial '9202'. The UA receiving the INVITE is on an internal host with address 10.0.2.200.
I could try 'replace_all("@cybertheque.org","");' but I would like some advice as to the nature of the problem as well. I would also need some test calls from the outside to debug the changes. Anyone willing to call a few times (and let me know before you do so I can make the changes to ser.cfg)?
Thanks,
Michael _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Greger V. Teigre wrote:
Michael Grigoni wrote:
(SER 0.8.99-dev19 openbsd/sparc w/local patches) Greetings:
We have rarely received INVITES from UAs not registered on our SER host (from the outside) but as I am setting up a means for a Internet users from foreign realms to listen to audio by making a call to a UA on our network it is now necessary to process foreign INVITES.
Well, sip:9202@cybertheque.org@10.0.2.200:5060 is obviously an invalid aor. Try to figure out where it comes from.
Indeed, that is the question.
I could try 'replace_all("@cybertheque.org","");' but I would like some advice
This is currently working for me...
I had requested some test calls but got no takers; I discovered a callback service which works well (and costs nothing):
http://www.sipbroker.com/sipbroker/action/callOut
A description of how to arrange a callback (cut and pasted from another user's web forum post):
Here's how to access a web page that will let you request an inbound call (for self-testing):
Go to www.sipbroker.com
Sign up for a free sip Broker account, using your chosen "IP dial" sip URI as your
"username" on sip Broker (and anything you want for your sip Broker password, as the sip Broker password does NOT have to match any password you are using in your adapter).
- Once you are signed into sip Broker, use the "EziDial" link on the right. This will
take you to a web page that lets you make VoIP calls directly. It will prompt you for your inbound sip URI (which should default to the userid you entered when signing up), and the sip Broker code you want to connect with (*393613 for Free World Dialup's "echo test" would be a good choice).
- Press on the "dial" button (after filling in your sip URI, and which place you are
trying to call). If all goes well, you will get an inbound call from sip Broker to your sip URI, and then as soon as that connects you will hear the outbound dialing to the sip Broker VoIP code you entered (which in the case *393613 reaches the "echo test" run by FWD).
Regards,
Michael
On 6/18/07, Michael Grigoni michael.grigoni@cybertheque.org wrote:
Greger V. Teigre wrote:
Michael Grigoni wrote:
(SER 0.8.99-dev19 openbsd/sparc w/local patches) Greetings:
We have rarely received INVITES from UAs not registered on our SER host (from the outside) but as I am setting up a means for a Internet users from foreign realms to listen to audio by making a call to a UA on our network it is now necessary to process foreign INVITES.
Well, sip:9202@cybertheque.org@10.0.2.200:5060 is obviously an invalid aor. Try to figure out where it comes from.
Indeed, that is the question.
As you got the irony but not the answer ... here it is: your AOR has 2 domain parts (2 parts after an @). That is wrong. Something is messing up with your proxy :)
Cesc
Cesc Santa wrote:
On 6/18/07, Michael Grigoni <michael.grigoni@cybertheque.org
<snip>
> Well, sip:9202@cybertheque.org@10.0.2.200:5060 <http://10.0.2.200:5060> is obviously an invalid > aor. Try to figure out where it comes from. Indeed, that is the question.As you got the irony but not the answer ... here it is: your AOR has 2 domain parts (2 parts after an @). That is wrong. Something is messing up with your proxy :)
Sorry, I thought that was obvious in my original post; my question was _where_ was that 2 part uri coming from ? A misconfigured UA? I didn't do a packet capture but I thought that the issue may have been raised somewhere before and was seeking comments ;)
I would have no control over unknown users' UAs.
Anyway, my solution is working.
Regards,
Michael
I'm sorry, but I thought the answer to the "where does it come from"-question was obvious: You have to figure it out. Simply by doing a SIP trace you can identify when the invalid aor pops up. Should be far faster than asking on the list... Some issues may have a very specific cause, this is not among those. g-)
Michael Grigoni wrote:
Cesc Santa wrote:
On 6/18/07, Michael Grigoni <michael.grigoni@cybertheque.org
<snip>
> Well, sip:9202@cybertheque.org@10.0.2.200:5060 <http://10.0.2.200:5060> is obviously an invalid > aor. Try to figure out where it comes from. Indeed, that is the question.As you got the irony but not the answer ... here it is: your AOR has 2 domain parts (2 parts after an @). That is wrong. Something is messing up with your proxy :)
Sorry, I thought that was obvious in my original post; my question was _where_ was that 2 part uri coming from ? A misconfigured UA? I didn't do a packet capture but I thought that the issue may have been raised somewhere before and was seeking comments ;)
I would have no control over unknown users' UAs.
Anyway, my solution is working.
Regards,
Michael _______________________________________________ Serusers mailing list Serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Cesc Santa -
Greger V. Teigre -
Michael Grigoni