There is now a Grandstream GXV3000 in my network (neat little
videophones, I must say).
However, when someone sends a presence event through my server, the
grandstream responds with a SIP packet and additional XML info:
U 99.101.102.103:5060 -> 172.17.240.240:54330
NOTIFY sip:1101XXXXXXX@172.17.240.240:54330 SIP/2.0.
Record-Route: <sip:99.101.102.103;ftag=f0a1719429e37564;lr=on>.
Via: SIP/2.0/UDP 99.101.102.103;branch=z9hG4bK4204.13bfa134.0.
Via: SIP/2.0/UDP 66.69.71.90:34202;branch=z9hG4bK04c43fa29c41b774.
From: <sip:1101ZZZZZZZ@proxy.ourdomain.com>;tag=f0a1719429e37564.
To: "Jessa"<sip:1101XXXXXXX@proxy.ourdomain.com>;tag=1b55e40b.
Contact: <sip:1101ZZZZZZZ@66.69.71.90:34202>.
Call-ID: ZjczZGMzOWEzMTk0NjhkMzRjMjI3ODZkNzIwMGIxZDA..
CSeq: 1843 NOTIFY.
User-Agent: Grandstream GXV3000 (HW 0101, Ch:0) 1.0.1.7.
Max-Forwards: 16.
Allow:
INVITE,ACK,CANCEL,BYE,NOTIFY,REFER,OPTIONS,INFO,SUBSCRIBE,UPDATE,PRACK.
Event: presence.
Subscription-State: active.
Content-Type: application/xpidf+xml.
Content-Length: 342.
P-hint: LR.
.
<?xml version="1.0"?>.
<!DOCTYPE presence.
PUBLIC "-//IETF//DTD RFCxxxx XPIDF 1.0//EN" "xpidf.dtd">.
<presence>.
<presentity
uri=""Jessa"<sip:1101XXXXXXX@proxy.ourdomain.com>;tag=1b55e40b;method=SUBSCRIBE"
/>.
<atom atomid="1000">.
<address uri="<sip:1101ZZZZZZZ@66.69.71.90:34202>">.
<status status="open" />.
</address>.
</atom>.
</presence>
The XML info is causing errors in the logs (which I've been ignoring for
now, but that's not really an optimal solution).
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_to : unexpected char [>]
in statu
s 4: <<<>> .
Aug 15 15:16:12 proxy ser[19620]: ERROR: get_hdr_field: bad to header
Aug 15 15:16:12 proxy ser[19620]: ERROR:maxfwd:is_maxfwd_present :
parsing MAX_F
ORWARD header failed!
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_uri: uri too short: <> (0)
Aug 15 15:16:12 proxy ser[19620]: is_user_in(): Error while parsing URI
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_to : unexpected char [>]
in statu
s 4: <<<>> .
Aug 15 15:16:12 proxy ser[19620]: ERROR: get_hdr_field: bad to header
Aug 15 15:16:12 proxy ser[19620]: find_first_route: Error while parsing
headers
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_uri: uri too short: <> (0)
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_sip_msg_uri: bad uri <>
Aug 15 15:16:12 proxy ser[19620]: WARNING: do_action:error in expression
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_to : unexpected char [>]
in statu
s 4: <<<>> .
Aug 15 15:16:12 proxy ser[19620]: ERROR: get_hdr_field: bad to header
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_to : unexpected char [>]
in statu
s 4: <<<>> .
Aug 15 15:16:12 proxy ser[19620]: ERROR: get_hdr_field: bad to header
Aug 15 15:16:12 proxy ser[19620]: find_credentials(): Error while
parsing header
s
Aug 15 15:16:12 proxy ser[19620]: pre_auth(): Error while looking for
credential
s
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_to : unexpected char [>]
in statu
s 4: <<<>> .
Aug 15 15:16:12 proxy ser[19620]: ERROR: get_hdr_field: bad to header
Aug 15 15:16:12 proxy ser[19620]: ERROR: parse_to : unexpected char [>]
in statu
s 4: <<<>> .
Aug 15 15:16:12 proxy ser[19620]: ERROR: get_hdr_field: bad to header
Aug 15 15:16:12 proxy ser[19620]: ERROR: build_res_buf_from_sip_req:
alas, parse
_headers failed
Aug 15 15:16:12 proxy ser[19620]: pre_auth(): Error while sending 400 reply
Other than forwarding presence information to a presence-capable server
that understands the XML, is there anything I can do on the SER side to
ignore the XML stuff so I don't get a screen full of error messages
every time a presence event comes through?
N.
Hi,
I am student and new to the Presence Model und Protocols.
I have in my student project the following scenario:
company A wants to develop a presence service PA. The presence service PA
should get the data from the presence server PB of an other Company B over
the Internet. The Presence information of PA should be made available in
the Company A for different applications.
my question:
can PA poll or subscribe all changed/updated Presence Information from PB
regularly. Or it should request the Presence Information of each Presentity
individually?
which Presence server can implement the presence service PA.
What should I do if PB uses another Protokoll?
Thank you and Best Regards
Koder
--
Psssst! Schon vom neuen GMX MultiMessenger gehört?
Der kanns mit allen: http://www.gmx.net/de/go/multimessenger
Hi,
i attempt to connect ser to a sip provider with user + password authentication.
if i get it right, i have to load the uac modul and insert following line:
modparam("uac","credential","user:sip-provider-ip:password"), but i can't find
the uac modul .. i hope anybody can help me ..
another way i tried is this one:
route[x] {
rewriteuri("username@sip-provider-ip");
rewriteuserpass("username:password");
rewritehost("sip-provider-ip");
forward("username:password@sip-provider-ip");
}
but it worked either. it comes always up with: get_connection(): Connection
not found in the pool ..
kind regards,
julia heller
--
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
Hi All
As I understand dialog may be terminated by DIALOG module, e.g. due
session timeout. In this situation module sends BYE timeout.
When RTPproxy used does it receive signal to close RTP session whel
local BYE generated?
One more question -- is it possible to terminate session when RTPproxy
does not get RTP packets for some predefined time? may be RTPproxy must
be extended?
Thanks!
--
CU,
Victor Gamov
Hi friends
I have been on the look out for someting related to performance counters
or statistics in SER.
If i browse through the code, I find, that there is #ifdef STAT macro
defined, which is used if STATs are enabled while compilation.
Now, when i try to do that, it looks for a SNMP module related files...
which it doesnt find...
On searching on internet i find a page saying SNMP is dead...
Can any one help me in finding out how to enable statistics for SER? It is
extremely urgent for me... please help ..
:((
Thanks
Parminder Nayyar
The information contained in this e-mail message is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you should return it to the sender immediately. Please note that while we scan all e-mails for viruses we cannot guarantee that any e-mail is virus-free and accept no liability for any damage caused by any virus transmitted by this email.
hi there,
i have a question about routing between SER and asterisk:
I run SER and * on the same machine, so i configured * to listen on port
5070 (sip.conf: bindport 5070).
Now i want to route all numbers that are not found in SER to *,
therefore i wrote to ser.cfg in the main route section:
if (!lookup("location")) {
#sl_send_reply("404", "nicht gefunden");
rewritehostport("192.168.2.183:5070");
route(1);
break;
};
route(1) is the following:
route[1] {
# -----------------------------------------------------------------
# Default Message Handler
# -----------------------------------------------------------------
if (!t_relay()) {
sl_reply_error();
};
}
i have two SER-users: 1000 and 1001
i have one * user: 1002
when i dial 1002 i get immediately 'User not found'
does anyone have a hint?