HiThanks for the reply, I however, do not know how to implement what you mentioned in your earlier mail. can you detail the steps? One of the openser users has suggested the following:
*******************************************
if (is_method('INVITE'))
{
# check if from URI domain equals 911operator.com
if ($fd == '911operator.com')
{
# relay stateless using request URI
forward();
exit;
}
else
{
# relay statefull using request URI
if (!t_relay())
{
sl_reply_error();
};
exit;
}
}
However, the function forward(); does not parse and gives error bad arguments. Can you suggest how to get this code working? I need it working asap.
Thanks again,
Padmaja
Hi Padmaja,
There is no other way around but just to implement a call back service
on your proxy. Save in DB the last caller hitting the 911 service and
when receiving the 8911, just load it and fwd to it.
regards,
bogdan
Padmaja wrote:
> Hi all,
>
> I have an issue, where the sip user dials 911 number and hangs up. The 911
> operator then calls back to the user using the call back command provided
> earlier say 8911 (there is a b2bua that interprets the call back number and
> routes the call to the specific user). This number is to be routed via the
> openser proxy to the b2bua. However, when the 911 calls back, proxy treats
> this number as a username and since there are no registrations to this 8911
> number (though this entry is present at the proxy, no device has registered
> with this number), it sends back "404 Not found". How can this be
> circumvented?
>
> Thanks,
> Padmaja
Hello all,
is it possible to completely drop a reply from failure_route? I know it is
possible to change the reply with t_reply, but I need the possibility to send
nothing back to the UAC.
--
Greetings,
Alex Hermann
I am attempting to use carrierroute for the first time, and the problem that
I am having is that when I attempt to place a call, I see the following in
stderror:
/usr/local/sbin/openser[32664]: New request - M=INVITE RURI=
sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T=
sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32664]: Callee is not local - M=INVITE RURI=
sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T=
sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32664]: Not normalized callee '1678XXXXXXX' to
E.164format - M=INVITE RURI=
sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T=
sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32664]: carrierroute:carrier_rewrite_msg: Domain too
big. (We only have 5 domains, you wanted 0.)
/usr/local/sbin/openser[32664]: Request leaving server, D-URI='<null>' -
M=INVITE RURI=sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T=
sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32667]: New request - M=INVITE RURI=
sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T=
sip:1678XXXXXXX@domain.com IP=72.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32660]: NAT-Reply - S=100 D=Trying F=
sip:1404XXXXXXX@domain.com T=sip:1678XXXXXXX@domain.com IP=72.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32667]: Proxy authentication failed - M=INVITE RURI=
sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T=
sip:1678XXXXXXX@domain.com IP=72.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32663]: NAT-Reply - S=407 D=Proxy Authentication
Required F=sip:1404XXXXXXX@domain.com T=sip:1678XXXXXXX@domain.com IP=
72.XXX.XXX.XXX ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
/usr/local/sbin/openser[32663]: Failure route for PSTN entered - M=INVITE
RURI=sip:1678XXXXXXX@domain.com F=sip:1404XXXXXXX@domain.com T=
sip:1678XXXXXXX@domain.com IP=204.XXX.XXX.XXX
ID=133DAB62-97D8-4A2C-8D68-BAA4EC4B310C(a)192.168.5.147
Thanks for any direction!!
At 10:55 02/11/2007, Stefan.Brozinski(a)materna.de wrote:
>Hello everybody
>
>there is a bug in SER that removes the last byte from a message body if
>this happens to be a binary zero.
>
>This may be the case when the Content-Type is something binary (i.e.
>*not* using "Content-Type: text/something").
>
>The bad code is in udp_server.c. It is present in SER 0.9.x a well as in
>2.0. I have reported it in the bug tracker as SER-324 and attached a
>comment which points out the bad section of the code.
>
>How shall I proceed to fix this bug?
Ideally submit a patch to JIRA...http://tracker.iptel.org/browse/SER
-jiri
>Best regards
>Stefan
>_______________________________________________
>Serusers mailing list
>Serusers(a)lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
--
Jiri Kuthan http://iptel.org/~jiri/
I need to be able to check the SIP response code to INVITE messages only. I don't care about BYE, CANCEL or anything else.
I tried putting a hint header in the INVITE when I sent it out, but the replies came back from the upstream provider with the header removed.
I tried setting a flag when an INVITE was received and using that. Didn't work.
How can I do this?
Is there a way to see what method a response is for? If there is, I could ignore everything that wasn't a response to an INVITE.
Thanks,
Doug.
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
Hi
I`d like to know if is possible to use 'openserctl' to find the number of sessions OpenSER is managing. I think that it isn't possible. Is there another way?
Thanks.
Bruno Machado
Abra sua conta no Yahoo! Mail, o único sem limite de espaço para armazenamento!
http://br.mail.yahoo.com/
Hi all,
Is openser able to parse and interpret a xml script contained, for example,
in the body of INVITE method ?
If it was possible, what kind of module I'd have to use ?
Regards,
Daniel
--
Daniel Grotti
________________________
e-mail : d.grotti(a)gmail.com