Heya,
This might be an obvious answer, but when I forward a packet to another box
using the forward() method, this seems to break the URI?
rewriteuri("sip:test@test.co.uk");
forward(x.x.x.x, 5060);
Now on my asterisk box and looking at ngrep, the test(a)test.co.uk has
disappeared, and asterisk takes the SIPDOMAIN as 'x.x.x.x', rather than
'test.com'.
Is this the desired behaviour? Is there a way to do what I want to do? I
need to be able to pick out the original SIPDOMAIN in asterisk even after
the packet has been forwarded by SER. People seem to have talked about doing
this, but I'm not sure how I can forward it without obliterating the URI.
Cheers,
Chris.
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.344 / Virus Database: 267.10.16/83 - Release Date: 26/08/2005
I am currently trying to do an xml-rpc call to usrloc.show_contacts.
The xml packet I am sending is the following
POST /RPC2 HTTP/1.0
User-Agent: Radio UserLand/7.1b7 (WinNT)
Host: localhost:5060
Content-Type: text/xml
Content-length: 131
<?xml version=\"1.0\"?>
<methodCall>
<methodName>usrloc.show_contacts</methodName>
<params>
</params>
</methodCall>
As a return packet I am getting
HTTP/1.0 200 OK
Via: SIP/2.0/UDP 127.0.0.1:32769
Server: Sip EXpress router (0.10.99-janakj_experimental (i386/linux))
Content-Length: 303
Warning: 392 127.0.0.1:5060 "Noisy feedback tells: pid=5820
req_src_ip=127.0.0.1 req_src_port=32769 in_uri=/RPC2 out_uri=/RPC2
via_cnt==1"
<?xml version="1.0" encoding="UTF-8"?>
<methodResponse>
<fault>
<value><struct>
<member><name>faultCode</name>
<value><i4>400</i4></value></member>
<member><name>faultString</name>
<value><string>More Parameters Expected</string></value></member>
</struct></value>
</fault>
</methodResponse>
This tells me that I am not entering the correct information, but I am
at a loss to exactly what else I should be inserting.
I did a search for rpc_show_contacts and found in
./sip_router/modules/usrloc/ul_rpc.c
static void rpc_show_contacts(rpc_t* rpc)
After searching some more I could not find the rpc_t structure. Does
anyone know what values I should be passing via XML?
Thanks,
Zach Keatts
Software Engineer
Nuvio.com
Hi,
IF I set auth_db:calculate_ha1=no, will the radius
authentication also be in non-digest (plaintext/basic) mode??
Reply please. Very urgent.
Regards,
Ashutosh Kumar
Hi!
I checked how SER would behave with large Max-Forwards values.
Paragraph 20.22 of RFC 3261 notes Max-Forwards to be anywhere between 0
and 255 but SER lacks a check for the upper boundry in the maxfwd module.
I'm not sure how the correct way to remove the broken header field and
introducing a correct one would be so I leave this for somebody who
knows :)
Hendrik
--
freenet Cityline GmbH, Hamburger Chaussee 2-4, 24114 Kiel, Germany
Phone: +49 (0)431 9020552, Fax: +49 (0)431 9020559
Internet: http://www.freenet.de, eMail: hendrik.scholz(a)freenet-ag.de
Hi!
I gave 3.1.2.4 of draft-ietf-sipping-torture-tests-07 a try and
sent
- a REGISTER with Expires > 2^31 and lower than 2^32
(2147483748 in my case).
- a REGISTER with Expires > 2^32
(4294967596 = 2^32 + 300)
I used print_expires() to print the resulting values SER (0.9.3 +
changes) parsed.
It's a negative value in first case and 300 in the latter one.
parser/parse_expires.h defines exp_body_t to have 'int val' which
is not enough to store the parsed values.
Changing it to 'unsigned int val' prevents the negative values from
coming up in SER but does not solve the main problem.
The draft stats that a default value of 3600 seconds should be
assumed in case of errors, so an additional check to make sure
_e->val will always be below 2^32 is necessary.
I do have a small patch for our non-standard branch and could wrap
one up for HEAD if needed.
Hendrik
--
freenet Cityline GmbH, Hamburger Chaussee 2-4, 24114 Kiel, Germany
Phone: +49 (0)431 9020552, Fax: +49 (0)431 9020559
Internet: http://www.freenet.de, eMail: hendrik.scholz(a)freenet-ag.de
Hi there,
The core "drop" statement has a new special meaning in some route types (by default it's equivalent to "exit"):
- BRANCH ROUTE - the request branch is discarded (not fwd);
- ONREPLY ROUTE - if provisional reply (<200), it will be discarded (not fwd, not stored, but only timers updated);
Wiki will be updated soon with this text ;)
regards,
bogdan
hello, somebody knows the true difference between this:
sip:1111@sip.domain.com y sip:1111 at sip.domain.com
Because in logs (with ngrep) only I see the URI default????? (sip:1111@.....)
Why i do not see the RURI???
Thanks
Hi all
i have multiple gateway devices to PSTN. All are equal in terms of what
destinations may be reached behind it or the termination costs. I use
multiple devices for two reasons: capacity and failover.
So what i need is functionality to hunt lines or at least doing a crank back
(or even better both). The best way to this (IMHO) would be to track the
line usage on each gateway and check it before routing to a gateway to make
sure, there is a line available to place the call to (this would be a kind
of line hunting). But i could also "live" with a solution that works more
like a failover mechanism. In that case i would route the call to the first
gateway in my list and if it is not available or has no more free lines, i
would need to detect this, take the call back and place it on another
gateway.
As far as i could find out, there is no hunting, failover or crank back
support directly built into SER. Is it possible to implement such
functionality using the "common" routing scripts in SER? Did anyone of you
ever had similar requirements and did you find a way to fullfill it?
I'm very thankfull for any idea, hint, snipplet, ....
Thanks a lot for your help.
Best Regards
Frank