Jump to content

Ipness doesn't work with pbxnsip 3.0


mathy
 Share

Recommended Posts

hi,

 

i'm curently testing the ITSP ipness.net and when i try to make a call from a pbxnsip 2.0.2.1676 , i can make my call with it but when he try the same configuration with ipness on my pbxnsip 3.2.0.3144 i have everytime en error :

 

here is my log from pbxnsip 3.2.0.3144 :

 

[2] 2009/02/10 17:13:20: SIP Rx udp:172.16.1.131:5060:

REGISTER sip:bizzvoice.bizzdev.net SIP/2.0

Via: SIP/2.0/UDP 172.16.1.131:5060;branch=z9hG4bK-5b20648b

From: <sip:528@bizzvoice.bizzdev.net>;tag=902f8fd69473f991o0

To: <sip:528@bizzvoice.bizzdev.net>

Call-ID: ee8491a9-742926da@172.16.1.131

CSeq: 10445 REGISTER

Max-Forwards: 70

Authorization: Digest username="528",realm="bizzvoice.bizzdev.net",nonce="8987719d17ac270f97e002098c465c59",uri="sip:bizzvoice.bizzdev.net",algorithm=MD5,response="f020b7f901db7b3bf8fed721f6a26156"

Contact: <sip:528@172.16.1.131:5060>;expires=3600

User-Agent: Linksys/SPA962-5.2.8(SC)

Content-Length: 0

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: replaces

 

 

[9] 2009/02/10 17:13:20: Resolve 33774: aaaa udp 172.16.1.131 5060

[9] 2009/02/10 17:13:20: Resolve 33774: a udp 172.16.1.131 5060

[9] 2009/02/10 17:13:20: Resolve 33774: udp 172.16.1.131 5060

[2] 2009/02/10 17:13:20: SIP Tx udp:172.16.1.131:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 172.16.1.131:5060;branch=z9hG4bK-5b20648b

From: <sip:528@bizzvoice.bizzdev.net>;tag=902f8fd69473f991o0

To: <sip:528@bizzvoice.bizzdev.net>;tag=76b0c49974

Call-ID: ee8491a9-742926da@172.16.1.131

CSeq: 10445 REGISTER

Contact: <sip:528@172.16.1.131:5060>;expires=358

Content-Length: 0

 

 

[2] 2009/02/10 17:13:21: SIP Rx udp:172.16.1.193:5060:

REGISTER sip:bizzvoice.bizzdev.net SIP/2.0

Via: SIP/2.0/UDP 172.16.1.193:5060;rport;branch=z9hG4bK768809449

From: <sip:552@bizzvoice.bizzdev.net>;tag=686220153

To: <sip:552@bizzvoice.bizzdev.net>

Call-ID: 1778449007@172.16.1.193

CSeq: 812 REGISTER

Contact: <sip:552@172.16.1.193:5060>

Max-Forwards: 5

User-Agent: Linphone-1.1.0 MX-Video/eXosip

Expires: 200

Content-Length: 0

 

 

[9] 2009/02/10 17:13:21: Resolve 33775: aaaa udp 172.16.1.193 5060

[9] 2009/02/10 17:13:21: Resolve 33775: a udp 172.16.1.193 5060

[9] 2009/02/10 17:13:21: Resolve 33775: udp 172.16.1.193 5060

[2] 2009/02/10 17:13:21: SIP Tx udp:172.16.1.193:5060:

SIP/2.0 200 Ok

Via: SIP/2.0/UDP 172.16.1.193:5060;rport=5060;branch=z9hG4bK768809449

From: <sip:552@bizzvoice.bizzdev.net>;tag=686220153

To: <sip:552@bizzvoice.bizzdev.net>;tag=a5e19bf91d

Call-ID: 1778449007@172.16.1.193

CSeq: 812 REGISTER

Contact: <sip:552@172.16.1.193:5060>;expires=61

Content-Length: 0

 

 

[2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060:

INVITE sip:4069665262@bizzvoice.bizzdev.net SIP/2.0

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 101 INVITE

Max-Forwards: 70

Contact: <sip:526@172.16.1.104:5060>

Expires: 240

User-Agent: Linksys/SPA942-6.1.3(a)

Content-Length: 399

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: replaces

Content-Type: application/sdp

 

v=0

o=- 10441819 10441819 IN IP4 172.16.1.104

s=-

c=IN IP4 172.16.1.104

t=0 0

m=audio 16398 RTP/AVP 0 2 4 8 18 96 97 98 101

a=rtpmap:0 PCMU/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:4 G723/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729a/8000

a=rtpmap:96 G726-40/8000

a=rtpmap:97 G726-24/8000

a=rtpmap:98 G726-16/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

 

[9] 2009/02/10 17:13:22: UDP: Opening socket on port 57986

[9] 2009/02/10 17:13:22: UDP: Opening socket on port 57987

[5] 2009/02/10 17:13:22: Identify trunk (domain name match) 13

[9] 2009/02/10 17:13:22: Resolve 33776: aaaa udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33776: a udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33776: udp 172.16.1.104 5060

[2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 101 INVITE

Content-Length: 0

 

 

[9] 2009/02/10 17:13:22: Resolve 33777: aaaa udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33777: a udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33777: udp 172.16.1.104 5060

[2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060:

SIP/2.0 401 Authentication Required

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 101 INVITE

User-Agent: pbxnsip-PBX/3.2.0.3144

WWW-Authenticate: Digest realm="bizzvoice.bizzdev.net",nonce="08f001656477b3f6bd5b13c6ea33dc89",domain="sip:4069665262@bizzvoice.bizzdev.net",algorithm=MD5

Content-Length: 0

 

 

[2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060:

ACK sip:4069665262@bizzvoice.bizzdev.net SIP/2.0

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-69aec261

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 101 ACK

Max-Forwards: 70

Contact: <sip:526@172.16.1.104:5060>

User-Agent: Linksys/SPA942-6.1.3(a)

Content-Length: 0

 

 

[2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060:

INVITE sip:4069665262@bizzvoice.bizzdev.net SIP/2.0

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 102 INVITE

Max-Forwards: 70

Authorization: Digest username="526",realm="bizzvoice.bizzdev.net",nonce="08f001656477b3f6bd5b13c6ea33dc89",uri="sip:4069665262@bizzvoice.bizzdev.net",algorithm=MD5,response="1d3f568d529de0be9c4ef3cba77a582c"

Contact: <sip:526@172.16.1.104:5060>

Expires: 240

User-Agent: Linksys/SPA942-6.1.3(a)

Content-Length: 399

Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER

Supported: replaces

Content-Type: application/sdp

 

v=0

o=- 10441819 10441819 IN IP4 172.16.1.104

s=-

c=IN IP4 172.16.1.104

t=0 0

m=audio 16398 RTP/AVP 0 2 4 8 18 96 97 98 101

a=rtpmap:0 PCMU/8000

a=rtpmap:2 G726-32/8000

a=rtpmap:4 G723/8000

a=rtpmap:8 PCMA/8000

a=rtpmap:18 G729a/8000

a=rtpmap:96 G726-40/8000

a=rtpmap:97 G726-24/8000

a=rtpmap:98 G726-16/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-15

a=ptime:30

a=sendrecv

 

[8] 2009/02/10 17:13:22: Tagging request with existing tag

[9] 2009/02/10 17:13:22: Resolve 33778: aaaa udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33778: a udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33778: udp 172.16.1.104 5060

[2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 102 INVITE

Content-Length: 0

 

 

[9] 2009/02/10 17:13:22: UDP: Opening socket on port 60732

[9] 2009/02/10 17:13:22: UDP: Opening socket on port 60733

[9] 2009/02/10 17:13:22: Resolve 33779: url sip:ipness.net:6060

[9] 2009/02/10 17:13:22: Resolve 33779: a udp ipness.net 6060

[9] 2009/02/10 17:13:22: Resolve 33779: udp 82.146.119.38 6060

[2] 2009/02/10 17:13:22: SIP Tx udp:82.146.119.38:6060:

INVITE sip:069665262@ipness.net:6060;user=phone SIP/2.0

Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport

From: <sip:tilleul@ipness.net:6060>;tag=31120

To: <sip:069665262@ipness.net:6060;user=phone>

Call-ID: d399edac@pbx

CSeq: 1885 INVITE

Max-Forwards: 70

Contact: <sip:tilleul@172.16.1.243:5060;transport=udp>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.2.0.3144

Content-Type: application/sdp

Content-Length: 290

 

v=0

o=- 64964 64964 IN IP4 172.16.1.243

s=-

c=IN IP4 172.16.1.243

t=0 0

m=audio 60732 RTP/AVP 0 8 9 2 3 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:9 g722/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:3 gsm/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=sendrecv

 

[9] 2009/02/10 17:13:22: Resolve 33780: aaaa udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33780: a udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33780: udp 172.16.1.104 5060

[2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060:

SIP/2.0 183 Ringing

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 102 INVITE

Contact: <sip:526@172.16.1.243:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.2.0.3144

Content-Type: application/sdp

Content-Length: 255

 

v=0

o=- 32019 32019 IN IP4 172.16.1.243

s=-

c=IN IP4 172.16.1.243

t=0 0

m=audio 57986 RTP/AVP 0 8 2 101

a=rtpmap:0 pcmu/8000

a=rtpmap:8 pcma/8000

a=rtpmap:2 g726-32/8000

a=rtpmap:101 telephone-event/8000

a=fmtp:101 0-16

a=ptime:30

a=sendrecv

 

[2] 2009/02/10 17:13:22: SIP Rx udp:82.146.119.38:6060:

SIP/2.0 100 Trying

Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport

From: <sip:tilleul@ipness.net:6060>;tag=31120

To: <sip:069665262@ipness.net:6060;user=phone>;tag=GR52RWG346-34

Call-ID: d399edac@pbx

CSeq: 1885 INVITE

Contact: "Verso CM" <sip:82.146.119.38:6060>

Allow-Events: refer

User-Agent: pbxnsip-PBX/3.2.0.3144

Content-Length: 0

 

 

[2] 2009/02/10 17:13:22: SIP Rx udp:82.146.119.38:6060:

SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport

From: <sip:tilleul@ipness.net:6060>;tag=31120

To: <sip:069665262@ipness.net:6060;user=phone>;tag=GR52RWG346-34

Call-ID: d399edac@pbx

CSeq: 1885 INVITE

Contact: "Verso CM" <sip:82.146.119.38:6060>

Allow-Events: refer

User-Agent: pbxnsip-PBX/3.2.0.3144

Content-Length: 0

 

 

[7] 2009/02/10 17:13:22: Call d399edac@pbx#31120: Clear last INVITE

[9] 2009/02/10 17:13:22: Resolve 33781: url sip:ipness.net:6060

[9] 2009/02/10 17:13:22: Resolve 33781: a udp ipness.net 6060

[9] 2009/02/10 17:13:22: Resolve 33781: udp 82.146.119.38 6060

[2] 2009/02/10 17:13:22: SIP Tx udp:82.146.119.38:6060:

ACK sip:069665262@ipness.net:6060;user=phone SIP/2.0

Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport

From: <sip:tilleul@ipness.net:6060>;tag=31120

To: <sip:069665262@ipness.net:6060;user=phone>;tag=GR52RWG346-34

Call-ID: d399edac@pbx

CSeq: 1885 ACK

Max-Forwards: 70

Contact: <sip:tilleul@172.16.1.243:5060;transport=udp>

Content-Length: 0

 

 

[5] 2009/02/10 17:13:22: INVITE Response 403 Forbidden: Terminate d399edac@pbx

[7] 2009/02/10 17:13:22: Other Ports: 1

[7] 2009/02/10 17:13:22: Call Port: fad0a7ad-c2a9bb11@172.16.1.104#865e9b91e7

[9] 2009/02/10 17:13:22: Resolve 33782: aaaa udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33782: a udp 172.16.1.104 5060

[9] 2009/02/10 17:13:22: Resolve 33782: udp 172.16.1.104 5060

[2] 2009/02/10 17:13:22: SIP Tx udp:172.16.1.104:5060:

SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 102 INVITE

Contact: <sip:526@172.16.1.243:5060>

Supported: 100rel, replaces, norefersub

Allow-Events: refer

Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE

Accept: application/sdp

User-Agent: pbxnsip-PBX/3.2.0.3144

Content-Length: 0

 

 

[2] 2009/02/10 17:13:22: SIP Rx udp:172.16.1.104:5060:

ACK sip:4069665262@bizzvoice.bizzdev.net SIP/2.0

Via: SIP/2.0/UDP 172.16.1.104:5060;branch=z9hG4bK-bdee5fa1

From: <sip:526@bizzvoice.bizzdev.net>;tag=9ff31efd79312c01o0

To: <sip:4069665262@bizzvoice.bizzdev.net>;tag=865e9b91e7

Call-ID: fad0a7ad-c2a9bb11@172.16.1.104

CSeq: 102 ACK

Max-Forwards: 70

Authorization: Digest username="526",realm="bizzvoice.bizzdev.net",nonce="08f001656477b3f6bd5b13c6ea33dc89",uri="sip:4069665262@bizzvoice.bizzdev.net",algorithm=MD5,response="1d3f568d529de0be9c4ef3cba77a582c"

Contact: <sip:526@172.16.1.104:5060>

User-Agent: Linksys/SPA942-6.1.3(a)

Content-Length: 0

Link to comment
Share on other sites

[2] 2009/02/10 17:13:22: SIP Rx udp:82.146.119.38:6060:

SIP/2.0 403 Forbidden

Via: SIP/2.0/UDP 172.16.1.243:5060;branch=z9hG4bK-9d0d48c8b3ed85de66e34b297e320015;rport

From: <sip:tilleul@ipness.net:6060>;tag=31120

To: <sip:069665262@ipness.net:6060;user=phone>;tag=GR52RWG346-34

Call-ID: d399edac@pbx

CSeq: 1885 INVITE

Contact: "Verso CM" <sip:82.146.119.38:6060>

Allow-Events: refer

User-Agent: pbxnsip-PBX/3.2.0.3144

Content-Length: 0

 

Hard to say why the provider sends forbidden back. Are you sure you paid your bills?

 

Interestingly, they seem to run pbxnsip as well. They even use the same version as you do!

Link to comment
Share on other sites

Hard to say why the provider sends forbidden back. Are you sure you paid your bills?

 

Interestingly, they seem to run pbxnsip as well. They even use the same version as you do!

 

yes i'm sure cause when I try with THE SAME ACCOUNT with SAME PARAMETERS on the pbxnsip 2.0.12 ... it work well and with the new it doesn't ... so there is maybe some differance between the two version ...

Link to comment
Share on other sites

hi, i have call to ipness to ask why the provider send me a forbidden call and he say me to use codec G729 but when i try to up this codec for this trunk , the codec doesn't move :( what can i do for force this codec for this trunk ?

There may be browser incompatibility with that page. It should work fine on IE. What browser are you using?

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...