6 Jul
2005
6 Jul
'05
4:22 a.m.
Hello,
Are the short notation of the SIP header names supported by the Proxy
functions that check various headers?
Example:
INVITE sip:+87810223334019@sip2sip.info SIP/2.0
v: SIP/2.0/UDP
192.168.0.8:5060;branch=z9hG4bK-10597899239c90aff5153ebe96e42c91;rport
f: "Blast" <sip:2233344162@sip2sip.info>;tag=19660
t: <sip:+87810223334019@sip2sip.info>
i: 1cc8c9c2(a)pbxnsip.com
CSeq: 1 INVITE
Max-Forwards: 69
m: <sip:2233344162@192.168.0.8:5060;transport=udp>
Supported: 100rel, replaces
Allow-Events: refer
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO
Accept: application/sdp
User-Agent: pbxnsip-PBX/0.95
c: application/sdp
l: 268
Regards,
Adrian
6 Jul
6 Jul
4:58 a.m.
Hi Adrian,
with short SIP headers, there are two parts:
internal parser - it is able to recognize the this format
script functions (textops -is_present_hf()) - SER version (based
only on header name comparison) was not able to match "contact" ==
"m"||
(is_present_hf("contact") didn't match the m: header); The OpenSER
version (based on header types comparison)) can do this.
So, I would say OpenSER has full support for short headers.
regards,
bogdan|| <http://www.openser.org/docs/modules/0.9.x/textops.html#AEN202>
Adrian Georgescu wrote:
Hello,
Are the short notation of the SIP header names supported by the Proxy
functions that check various headers?
Example:
INVITE sip:+87810223334019@sip2sip.info SIP/2.0
v: SIP/2.0/UDP
192.168.0.8:5060;branch=z9hG4bK-10597899239c90aff5153ebe96e42c91;rport
f: "Blast" <sip:2233344162@sip2sip.info>;tag=19660
t: <sip:+87810223334019@sip2sip.info>
i: 1cc8c9c2(a)pbxnsip.com
CSeq: 1 INVITE
Max-Forwards: 69
m: <sip:2233344162@192.168.0.8:5060;transport=udp>
Supported: 100rel, replaces
Allow-Events: refer
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO
Accept: application/sdp
User-Agent: pbxnsip-PBX/0.95
c: application/sdp
l: 268
Regards,
Adrian
_______________________________________________
Users mailing list
Users(a)openser.org
http://openser.org/cgi-bin/mailman/listinfo/users
5:14 a.m.
Hello,
On 07/06/05 11:58, Bogdan-Andrei Iancu wrote:
Hi Adrian,
with short SIP headers, there are two parts:
internal parser - it is able to recognize the this format
script functions (textops -is_present_hf()) - SER version (based
only on header name comparison) was not able to match "contact" ==
"m"|| (is_present_hf("contact") didn't match the m: header); The
OpenSER version (based on header types comparison)) can do this.
So, I would say OpenSER has full support for short headers.
just to give some other examples: the pseudo-variables that are
references to headers recognize the compact and normal header names. So,
xlog(), xdbg(), avp_printf(), subst(), subst_uri() and subst_user() can
also deal with compact headers.
Cheers,
Daniel
regards,
bogdan|| <http://www.openser.org/docs/modules/0.9.x/textops.html#AEN202>
Adrian Georgescu wrote:
Hello,
Are the short notation of the SIP header names supported by the Proxy
functions that check various headers?
Example:
INVITE sip:+87810223334019@sip2sip.info SIP/2.0
v: SIP/2.0/UDP
192.168.0.8:5060;branch=z9hG4bK-10597899239c90aff5153ebe96e42c91;rport
f: "Blast" <sip:2233344162@sip2sip.info>;tag=19660
t: <sip:+87810223334019@sip2sip.info>
i: 1cc8c9c2(a)pbxnsip.com
CSeq: 1 INVITE
Max-Forwards: 69
m: <sip:2233344162@192.168.0.8:5060;transport=udp>
Supported: 100rel, replaces
Allow-Events: refer
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, PRACK, INFO
Accept: application/sdp
User-Agent: pbxnsip-PBX/0.95
c: application/sdp
l: 268
Regards,
Adrian
_______________________________________________
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
7086
days inactive
7086
days old
2 comments
3 participants
participants (3)
-
Adrian Georgescu -
Bogdan-Andrei Iancu -
Daniel-Constantin Mierla