Open Source Sip: [OpenSIPStack] Réf. : Re: Réf. : ...

1 Replies Last post: Aug 23, 2007 6:27 AM by Guest

Guest

Aug 23, 2007 6:17 AM

[OpenSIPStack] Réf. : Re: Réf. : Re: Réf. : Re: sipXecs and openSBC

Yes, I can register directly to the Registrar.
Any comment Joegen ?

I remarks also that even the registrar accept ( i configure to accept all
) the registration, it always return the 401 response first.
Is this happen to ur case ?

BR,
Kolneath SOMETH

"Gaurav Kheterpal"

Envoyé par : opensipstack-devel-bounces at lists dot sourceforge dot net
23/08/2007 12:14
Veuillez répondre à opensipstack-devel
Remis le : 23/08/2007 12:13

Pour :
cc : , (ccc : Kolneath
SOMETH/DRD/SAGEM)
Objet : Re: [OpenSIPStack] Réf. : Re: Réf. : Re: sipXecs and openSBC

I believe that it should work fine if you put the IP address of SBC in
your
registrar address.

A 401 response indicates that the registrar challenged you for
credentials.
For whatever reasons, the registrar returns a 403 Forbidden when you
re-send
the REGISTER request with credentials.

Are you able to register directly UA Registrar (without OpenSBC in
between)? This should help eliminate any problem with credentials provided
by you.

Regards,
Gaurav

-----Original Message-----
From: opensipstack-devel-bounces at lists dot sourceforge dot net
[mailto:opensipstack-devel-bounces at lists dot sourceforge dot net] On Behalf Of
Kolneath SOMETH
Sent: Thursday, August 23, 2007 3:21 PM
To: opensipstack-devel at lists dot sourceforge dot net
Cc: opensipstack-devel-bounces at lists dot sourceforge dot net; opensipstack-
devel at lists dot sourceforge dot net
Subject: [OpenSIPStack] Réf. : Re: Réf. : Re: sipXecs and openSBC

Thank you Andre n Gaurav,

I use version 3 build 29712 of X-lite.
By the way, I already configured my OSBC to be Upper Reg. So in client,

put the @ of this OSBC in the registrar text field or u put the @ of the
registrar ?

I tried in the OSS Phone by putting @ of OSBC in the registrar text

field

and leave Outbound Proxy text field empty...but it seems doesn't
work...here is its result :
192.168.100.1 -> @ of my OSBC
I also put [sip:*@192.168.100.1:*] sip:192.168.200.2:5060 in the
B2BUpperReg route to route the request to 192.168.200.2 (@ of registrar)

SEND: XOR=0 457 Bytes to 192.168.100.1:5060:UDP (REGISTER
sip:192.168.100.1 SIP/2.0) Interface Address=
REGISTER sip:192.168.100.1 SIP/2.0
From: kolneath
;tag=cf86c30279f9181083f1cdbc5878f183
To: sip:kolneath@192.168.100.1
Via: SIP/2.0/UDP

192.168.100.5:5060;iid=1;branch=z9hG4bKe98cc30279f9181083f1cdbc5878f183;ua

s-addr=192.168.100.1;rport
CSeq: 1 REGISTER
Call-ID: cf86c302-79f9-1810-9ccf-cdbc5878f183
Contact: "kolneath" <sip:kolneath@192.168.100.5:5060;transport=udp>
Expires: 3600
Max-Forwards: 70
Content-Length: 0

----------------20:38:10.987----------------
RCV: XOR=0 561 Bytes from RCVADDR: 192.168.100.1:RCVPORT: 5060:UDP
(SIP/2.0 401 Unauthorized)
SIP/2.0 401 Unauthorized
From: kolneath
;tag=cf86c30279f9181083f1cdbc5878f183
To: ;tag=bc93f6ae8448dc11980dda3af2250d78
Via: SIP/2.0/UDP

192.168.100.5:5060;iid=1;branch=z9hG4bKe98cc30279f9181083f1cdbc5878f183;ua

s-addr=192.168.100.1;rport=5060;received=192.168.100.5
CSeq: 1 REGISTER
Call-ID: cf86c302-79f9-1810-9ccf-cdbc5878f183
WWW-Authenticate: Digest realm="192.168.100.1",
nonce="0db5267eb085c56c3614fa08cb961420",
opaque="948bdb3d1f6f8991f01ec841a03ec0ea", algorithm=MD5
Content-Length: 0

----------------20:38:10.998----------------
SEND: XOR=0 650 Bytes to 192.168.100.1:5060:UDP (REGISTER
sip:192.168.100.1 SIP/2.0) Interface Address=
REGISTER sip:192.168.100.1 SIP/2.0
From: kolneath
;tag=aef4c30279f9181083f1cdbc5878f183
To: sip:kolneath@192.168.100.1
Via: SIP/2.0/UDP

192.168.100.5:5060;iid=1;branch=z9hG4bKaef4c30279f9181083f2cdbc5878f183;ua

s-addr=192.168.100.1;rport
CSeq: 2 REGISTER
Call-ID: cf86c302-79f9-1810-9ccf-cdbc5878f183
Contact: "kolneath" <sip:kolneath@192.168.100.5:5060;transport=udp>
Expires: 3600
Max-Forwards: 70
Authorization: Digest username="kolneath", realm="192.168.100.1",
nonce="0db5267eb085c56c3614fa08cb961420", uri="sip:192.168.100.1",
response="ba97a81e09441d0cae165ce580060d2b", algorithm=MD5
Content-Length: 0

----------------20:38:11.050----------------
RCV: XOR=0 410 Bytes from RCVADDR: 192.168.100.1:RCVPORT: 5060:UDP
(SIP/2.0 403 Forbidden)
SIP/2.0 403 Forbidden
From: kolneath
;tag=aef4c30279f9181083f1cdbc5878f183
To: ;tag=b2c4fcae8448dc11980dda3af2250d78
Via: SIP/2.0/UDP

192.168.100.5:5060;iid=1;branch=z9hG4bKaef4c30279f9181083f2cdbc5878f183;ua

s-addr=192.168.100.1;rport=5060;received=192.168.100.5
CSeq: 2 REGISTER
Call-ID: cf86c302-79f9-1810-9ccf-cdbc5878f183
Content-Length: 0

Any idea ?

Kolneath SOMETH

"Gaurav Kheterpal"

Envoyé par : opensipstack-devel-bounces at lists dot sourceforge dot net
23/08/2007 11:32
Veuillez répondre à opensipstack-devel
Remis le : 23/08/2007 11:32

Pour : ,

cc : (ccc : Kolneath SOMETH/DRD/SAGEM)
Objet : Re: [OpenSIPStack] Réf. : Re: sipXecs and openSBC

Hello,

But i don know how to configure with others SIP clients for example
X-Lite or 3CX as their interfaces don't have Outbound Proxy. They have
only Proxy/Registrar and domain.

GK>> unless you have an outdated version of Xlite, you can find the
Outbound
Proxy setting under System Settings -> SIP Proxy > Outbound Proxy & Use
Outbound Proxy

Either way, you can enable the Upper Registration mode in OpenSBC &

still

be
able to register with your registrar without using outbound proxy.

Refer to
http://www.opensourcesip.org:8080/JSPWiki/Wiki.jsp?page=UpperRegistrationH
ow
to

I hope this helps.

Regards,
Gaurav

opensipstack

sip servers ?
Here is my platform test :

UA B2BUA Reg(OpenSBC) Registrar

Normally, i configure my OSS phone with these configurations :
registrar : @ of registrar
outbound proxy : @ of B2BUA Reg

But i don know how to configure with others SIP clients for example
X-Lite or 3CX as their interfaces don't have Outbound Proxy. They have
only Proxy/Registrar and domain.

Any help appreciated,

Kolneath SOMETH

" Ce courriel et les documents qui y sont attaches peuvent contenir

des

informations confidentielles. Si vous n'etes pas le destinataire
escompte, merci d'en informer l'expediteur immediatement et de

detruire

courriel ainsi que tous les documents attaches de votre systeme
informatique. Toute divulgation, distribution ou copie du present

courriel

et des documents attaches sans autorisation prealable de son emetteur

est

interdite."

" This e-mail and any attached documents may contain confidential or
proprietary information. If you are not the intended recipient, please
advise the sender immediately and delete this e-mail and all attached
documents from your computer system. Any unauthorised disclosure,
distribution or copying hereof is prohibited."

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a

browser.

Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel at lists dot sourceforge dot net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
opensipstack-devel mailing list
opensipstack-devel at lists dot sourceforge dot net
https://lists.sourceforge.net/lists/listinfo/opensipstack-devel

courriel ainsi que tous les documents attaches de votre systeme
informatique. Toute divulgation, distribution ou copie du present

courriel

et des documents attaches sans autorisation prealable de son emetteur

est

" Ce courriel et les documents qui y sont attaches peuvent contenir des informations confidentielles. Si vous n'etes pas le destinataire escompte, merci d'en informer l'expediteur immediatement et de detruire ce courriel ainsi que tous les documents attaches de votre systeme informatique. Toute divulgation, distribution ou copie du present courriel et des documents attaches sans autorisation prealable de son emetteur est interdite."

" This e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, please advise the sender immediately and delete this e-mail and all attached documents from your computer system. Any unauthorised disclosure, distribution or copying hereof is prohibited."

Guest

1. Aug 23, 2007 6:27 AM

in response to: Guest

Re: [OpenSIPStack] Réf. : Re: Réf. : Re: Réf. : Re: sipXecs and openSBC

A 401 response is normal as its part of the challenge handshake
authentication process. Refer to Section 22.2 in RFC 3261:-

INVITE (Without credentials) 401 INVITE (With credentials) 200
OK.

Regards,
Gaurav

-----Original Message-----
From: opensipstack-devel-bounces at lists dot sourceforge dot net
[mailto:opensipstack-devel-bounces at lists dot sourceforge dot net] On Behalf Of
Kolneath SOMETH
Sent: Thursday, August 23, 2007 3:47 PM
To: opensipstack-devel at lists dot sourceforge dot net
Cc: opensipstack-devel at lists dot sourceforge dot net; opensipstack-devel-
bounces at lists dot sourceforge dot net
Subject: [OpenSIPStack] Réf. : Re: Réf. : Re: Réf. : Re: sipXecs and
openSBC

Yes, I can register directly to the Registrar.
Any comment Joegen ?

I remarks also that even the registrar accept ( i configure to accept all
) the registration, it always return the 401 response first.
Is this happen to ur case ?

BR,
Kolneath SOMETH

"Gaurav Kheterpal"

Envoyé par : opensipstack-devel-bounces at lists dot sourceforge dot net
23/08/2007 12:14
Veuillez répondre à opensipstack-devel
Remis le : 23/08/2007 12:13

Pour :
cc : , (ccc :
Kolneath
SOMETH/DRD/SAGEM)
Objet : Re: [OpenSIPStack] Réf. : Re: Réf. : Re:
sipXecs and openSBC

put the @ of this OSBC in the registrar text field or u put the @ of the
registrar ?

I tried in the OSS Phone by putting @ of OSBC in the registrar text

field

192.168.100.5:5060;iid=1;branch=z9hG4bKe98cc30279f9181083f1cdbc5878f183;ua

192.168.100.5:5060;iid=1;branch=z9hG4bKaef4c30279f9181083f2cdbc5878f183;ua

s-addr=192.168.100.1;rport=5060;received=192.168.100.5
CSeq: 2 REGISTER
Call-ID: cf86c302-79f9-1810-9ccf-cdbc5878f183
Content-Length: 0

Any idea ?

Kolneath SOMETH

"Gaurav Kheterpal"

Envoyé par : opensipstack-devel-bounces at lists dot sourceforge dot net
23/08/2007 11:32
Veuillez répondre à opensipstack-devel
Remis le : 23/08/2007 11:32

Pour : ,

cc : (ccc : Kolneath SOMETH/DRD/SAGEM)
Objet : Re: [OpenSIPStack] Réf. : Re: sipXecs and openSBC

Hello,

But i don know how to configure with others SIP clients for example
X-Lite or 3CX as their interfaces don't have Outbound Proxy. They have
only Proxy/Registrar and domain.

still

be
able to register with your registrar without using outbound proxy.

Refer to

http://www.opensourcesip.org:8080/JSPWiki/Wiki.jsp?page=UpperRegistrationH

ow
to

I hope this helps.

Regards,
Gaurav

opensipstack

" Ce courriel et les documents qui y sont attaches peuvent contenir

des

informations confidentielles. Si vous n'etes pas le destinataire
escompte, merci d'en informer l'expediteur immediatement et de

detruire

courriel ainsi que tous les documents attaches de votre systeme
informatique. Toute divulgation, distribution ou copie du present

courriel

et des documents attaches sans autorisation prealable de son emetteur

est

This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a

browser.

courriel ainsi que tous les documents attaches de votre systeme
informatique. Toute divulgation, distribution ou copie du present

courriel

et des documents attaches sans autorisation prealable de son emetteur

est

" Ce courriel et les documents qui y sont attaches peuvent contenir des
informations confidentielles. Si vous n'etes pas le destinataire
escompte, merci d'en informer l'expediteur immediatement et de detruire ce
courriel ainsi que tous les documents attaches de votre systeme
informatique. Toute divulgation, distribution ou copie du present courriel
et des documents attaches sans autorisation prealable de son emetteur est
interdite."

" This e-mail and any attached documents may contain confidential or
proprietary information. If you are not the intended recipient, please
advise the sender immediately and delete this e-mail and all attached
documents from your computer system. Any unauthorised disclosure,
distribution or copying hereof is prohibited."

Aug 23, 2007 6:17 AM

[OpenSIPStack] Réf. : Re: Réf. : Re: Réf. : Re: sipXecs and openSBC

Actions

More Like This