Andreas Greulich
2005-Apr-05 11:24 UTC
[Asterisk-Users] PortaSIP/PortaBilling incompatibility (provider: sipcall.ch)
Hi all,
Using the Swiss VoIP provider "sipcall.ch" (same software as
"citytell.ch" and
"voip-guest.ch") I seem to be unable to successfully authenticate,
while X-Lite
is able to authenticate. From messages earlier posted in this mailing list
(<http://lists.digium.com/pipermail/asterisk-users/2004-November/071986.html>
and
<http://lists.digium.com/pipermail/asterisk-users/2004-December/075781.html>)
the problem seems to be "some authentication features" that were
missing...
unfortunately I didn't really understand the problem as described in these
mailings. From the link
<http://forum.portaone.com/index.php?act=Print&client=printer&f=3&t=236>
one
could suppose that there's a Cisco Radius fetaure missing (but I'm not
sure
about it). On Wikipedia, I found the info at
<http://www.voip-info.org/wiki-PortaOne+Radius+auth> - which I tried to
install,
but still no success. After all I think these patches only add Radius
capabilities allowing * to authenticate calling clients, but it probably has
nothing to do with * authenticating itself to a system using PortaSIP. Or am I
missing something? What exactly _IS_ the problem?
This is my (shortened) sip debug output from a unsuccessful call setup:
We're at 217.162.x.x port 15976
Answering with preferred capability 0x100 (g729)
12 headers, 8 lines
Reliably Transmitting:
INVITE sip:012345678@sip.backbone.ch SIP/2.0
Via: SIP/2.0/UDP 217.162.x.x:5060;branch=z9hG4bK23e58795;rport
From: "a109aa974d488ea0@10.1.41.188"
<sip:4131560xxxx@sip.backbone.ch>;tag=as2b204fcc
To: <sip:012345678@sip.backbone.ch>
Contact: <sip:4131560xxxx@217.162.x.x>
Call-ID: 2b11599f026e226d0b1cd05039544328@sip.backbone.ch
CSeq: 102 INVITE
User-Agent: Asterisk PBX
Date: Sat, 02 Apr 2005 06:55:47 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Content-Type: application/sdp
Content-Length: 162
...
Sip read:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 217.162.x.x:5060;branch=z9hG4bK23e58795;rport=5060
From: "a109aa974d488ea0@10.1.41.188"
<sip:4131560xxxx@sip.backbone.ch>;tag=as2b204fcc
To:
<sip:012345678@sip.backbone.ch>;tag=baea45a7611d9ef776323b3fa79b3a0b.ed74
Call-ID: 2b11599f026e226d0b1cd05039544328@sip.backbone.ch
CSeq: 102 INVITE
WWW-Authenticate: Digest realm="sip.backbone.ch",
nonce="424e4320515ae425dee06c2f8d1bf85d1b77a0aa"
Server: Sip EXpress router (0.8.14 (i386/freebsd))
Content-Length: 0
9 headers, 0 lines
Transmitting:
ACK sip:012345678@sip.backbone.ch SIP/2.0
...
Reliably Transmitting:
INVITE sip:012345678@sip.backbone.ch SIP/2.0
Via: SIP/2.0/UDP 217.162.x.x:5060;branch=z9hG4bK55571a6e;rport
From: "a109aa974d488ea0@10.1.41.188"
<sip:4131560xxxx@sip.backbone.ch>;tag=as2b204fcc
To: <sip:012345678@sip.backbone.ch>
Contact: <sip:4131560xxxx@217.162.x.x>
Call-ID: 2b11599f026e226d0b1cd05039544328@sip.backbone.ch
CSeq: 103 INVITE
User-Agent: Asterisk PBX
Authorization: Digest username="4131560xxxx",
realm="sip.backbone.ch",
algorithm=MD5, uri="sip:012345678@sip.backbone.ch",
nonce="424e4320515ae425dee06c2f8d1bf85d1b77a0aa",
response="40b24ce71b70c2d61df88c88e38c6428", opaque=""
Date: Sat, 02 Apr 2005 06:55:48 GMT
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER
Content-Type: application/sdp
Content-Length: 162
...
Sip read:
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 217.162.x.x:5060;branch=z9hG4bK55571a6e;rport=5060
From: "a109aa974d488ea0@10.1.41.188"
<sip:4131560xxxx@sip.backbone.ch>;tag=as2b204fcc
To:
<sip:012345678@sip.backbone.ch>;tag=baea45a7611d9ef776323b3fa79b3a0b.0e8a
Call-ID: 2b11599f026e226d0b1cd05039544328@sip.backbone.ch
CSeq: 103 INVITE
WWW-Authenticate: Digest realm="sip.backbone.ch",
nonce="424e4320515ae425dee06c2f8d1bf85d1b77a0aa"
Server: Sip EXpress router (0.8.14 (i386/freebsd))
Note that there was no NATting involved. Registration was previously done fine
as well:
Responding to challenge, registration to domain/host name sip.backbone.ch
12 headers, 0 lines
Reliably Transmitting:
REGISTER sip:sip.backbone.ch SIP/2.0
Via: SIP/2.0/UDP 217.162.x.x:5060;branch=z9hG4bK4bfc5242
From: <sip:4131560xxxx@sip.backbone.ch>;tag=as4204ee27
To: <sip:4131560xxxx@sip.backbone.ch>
Call-ID: 7f58a0b42795678e3e9882283adf4cf7@10.1.1.1
CSeq: 103 REGISTER
User-Agent: Asterisk PBX
Authorization: Digest username="4131560xxxx",
realm="sip.backbone.ch",
algorithm=MD5, uri="sip:sip.backbone.ch",
nonce="4252344d4ed23eb90a7f665ad041bdb780951dcd",
response="49ec64ca6598d8de5513e95baf581324", opaque=""
Expires: 1800
Contact: <sip:FromSipcall@217.162.x.x>
Event: registration
Content-Length: 0
(no NAT) to 212.117.200.148:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 217.162.x.x:5060;branch=z9hG4bK4bfc5242
From: <sip:4131560xxxx@sip.backbone.ch>;tag=as4204ee27
To:
<sip:4131560xxxx@sip.backbone.ch>;tag=ae6df1c1af36443e2e31c70c67056cf2-7038
Call-ID: 7f58a0b42795678e3e9882283adf4cf7@10.1.1.1
CSeq: 103 REGISTER
PortaBilling: available-funds:0.10 currency:CHF
Contact: <sip:FromSipcall@217.162.x.x>;expires=1795
Server: Sip EXpress router (0.9.0 (i386/freebsd))
Content-Length: 0
For comparison, this is a (sniffed) authentication packet using X-Lite (which
was successful - this time there is NATting involved, but it is still working):
Session Initiation Protocol
Request-Line: INVITE sip:012345678@sip.backbone.ch SIP/2.0
Method: INVITE
Resent Packet: False
Message Header
Via: SIP/2.0/UDP
10.1.41.186:5060;rport;branch=z9hG4bK0CD66CED6B3447569BF3C6A6E7829D0B
From: Sipcall <sip:4131560xxxx@sip.backbone.ch>;tag=3802584274
SIP Display info: Sipcall
SIP from address: sip:4131560xxxx@sip.backbone.ch
SIP tag: 3802584274
To: <sip:012345678@sip.backbone.ch>
SIP to address: sip:012345678@sip.backbone.ch
Contact: <sip:4131560xxxx@10.1.41.186:5060>
Call-ID: 71BCC915-1CD9-4B04-B544-91F736283D0E@10.1.41.186
CSeq: 57677 INVITE
Authorization: Digest
username="4131560xxxx",realm="sip.backbone.ch",nonce="424db3bdc70fcaa0c73a4b69c62d0630dc43cf2d",response="d411cabe15d23bb3b47f2706a526e7d7",uri="sip:012345678@sip.backbone.ch"
Max-Forwards: 70
Content-Type: application/sdp
User-Agent: X-Lite release 1103a
Content-Length: 300
Any help for this problem would be highly wecome.. thanks in advance!
--
Andreas Greulich
E-Mail: andreas.greulich@spl.ch
Skype: klaymen-neverhood
Sermo datur cunctis, animi sapientia paucis.
gramels
2005-Apr-11 11:18 UTC
[Asterisk-Users] PortaSIP/PortaBilling incompatibility (provider: sipcall.ch)
On Apr 5, 2005 8:24 PM, Andreas Greulich <andreas.greulich@spl.ch> wrote:> Hi all, > > Using the Swiss VoIP provider "sipcall.ch" (same software as "citytell.ch" and > "voip-guest.ch") I seem to be unable to successfully authenticate, while X-Lite > is able to authenticate. From messages earlier posted in this mailing list > (<http://lists.digium.com/pipermail/asterisk-users/2004-November/071986.html> > and > <http://lists.digium.com/pipermail/asterisk-users/2004-December/075781.html>) > the problem seems to be "some authentication features" that were missing... > unfortunately I didn't really understand the problem as described in these > mailings. From the link > <http://forum.portaone.com/index.php?act=Print&client=printer&f=3&t=236> one > could suppose that there's a Cisco Radius fetaure missing (but I'm not sure > about it). On Wikipedia, I found the info at > <http://www.voip-info.org/wiki-PortaOne+Radius+auth> - which I tried to install, > but still no success. After all I think these patches only add Radius > capabilities allowing * to authenticate calling clients, but it probably has > nothing to do with * authenticating itself to a system using PortaSIP. Or am I > missing something? What exactly _IS_ the problem? >I had the same issue. Received the following reply from sipcall support and the portasip vendor: --- If Useragent field in this config corresponds to User-Agent field in Asterisk's SIP messages and you may change it to something that doesn't contain a word Asterisk - please try to do so; in such case PortaSIP will not apply remote IP auth. --- after putting useragent=portasipfriendly (not asterisk) in the sip.conf general section all worked fine seems a starnge piece of code to me... -L