dslreports logo
Forums → VOIP etc → VOIP →

VOIP Tech Chat → Re: [Other] HKBN 2b PAP2 config

 uniqs
3
Share
« [Other] ubifone VOIP - http://www.ubifone.com • Cheapest DID ? »
This is a sub-selection from [Other] HKBN 2b PAP2 config
dikyee
join:2005-10-31
Vancouver, BC

dikyee to im_chandave

Member

2005-Dec-8 5:38 pm

to im_chandave

Re: [Other] HKBN 2b PAP2 config

Tks.have sent you the dmp report via IM,please check .tks
· actions · 2005-Dec-8 5:38 pm ·
im_chandave
Premium Member
join:2005-07-28
Cleveland, OH

im_chandave

Premium Member

2005-Dec-8 9:39 pm

I'm sorry Sunny. The stuff you cut and pasted into the IM you sent me did not have any information I can use to diagnose the problem. I really need the binary capture file generated by the 'windump -w hkbn.dmp ...' command.

Additionally, the traffic captures really need to have all the stuff I was asking you to capture. The stuff needed for the syslog dump from the PAP2 can be found in this posting: http://www.broadbandreports.com/forum/remark,14588534~days=9999~start=40;iframe=1#14942708. The stuff for the tcpdump would be:
  1. SIP INVITE from your softphone to HKBN
  2. HKBN 100/183 Trying
  3. HKBN 200 OK
  4. HKBN declaration of the RTP ports
  5. BYE (from either HKBN or the softphone
  6. 100/183 Trying (from either HKBN or the softphone)
  7. 200 OK (from either HKBN or softphone).

Without all that stuff, it's not worth sending the dumps and the logs to me. I won't be able to trace the conversation properly.

Sorry.

See ya...

d.c.
· actions · 2005-Dec-8 9:39 pm ·
nc22
join:2004-04-16
Everett, WA

nc22

Member

2005-Dec-31 11:37 pm

Hi Dave,

Happy new year, long time no see, as my hkbn was working for outgoing calls :P, however, it was not working again, I got busy signal when I have any outgoing call right after I punched in the phone number, do you have any suggestion? my firmware for my ata was sipura-2000 3.1.5, here is my log for the busy signal for every outgoing calls:

PLEASE HELP ;)

RSE_DEBUG: reference domain:s21.hkbntel.net
[0:5060]->203.80.89.135:5060
[0:5060]->203.80.89.135:5060
INVITE sip:92448888@s2hkbntel.net SIP/2.0
Via: SIP/2.0/UDP 192.168.2.8:5060;branch=z9hG4bK-f516699c
From: ;tag=f8fdd4d54e47c034o0
To:
Call-ID: af3b5629-f10e0ef0@192.168.2.8
CSeq: 101 INVITE
Max-Forwards: 70
Contact:
Expires: 240
User-Agent: Sipura/SPA2000-3.1.5
Content-Length: 229
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
Supported: x-sipura
Content-Type: application/sdp

v=0
o=- 58502 58502 IN IP4 192.168.2.8
s=-
c=IN IP4 192.168.2.8
t=0 0
m=audio 19388 RTP/AVP 8 100 101
a=rtpmap:8 PCMA/8000
a=rtpmap:100 NSE/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=sendrecv

[0:5060]
f: ;tag=f8fdd4d54e47c034o0
i: af3b5629-f10e0ef0@192.168.2.8
CSeq: 101 INVITE
v: SIP/2.0/UDP 192.168.2.8:5060;received=61.18.11.60;branch=z9hG4bK-f516699c
Server: MCS5x00_3.0
k: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec
l: 0

[0:5060];tag=324660314
f: ;tag=f8fdd4d54e47c034o0
i: af3b5629-f10e0ef0@192.168.2.8
CSeq: 101 INVITE
v: SIP/2.0/UDP 192.168.2.8:5060;received=61.18.11.60;branch=z9hG4bK-f516699c
k: com.nortelnetworks.firewall,p-3rdpartycontrol,nosec
l: 0

[0:5060]->203.80.89.135:5060
[0:5060]->203.80.89.135:5060
ACK sip:92448888@s2hkbntel.net SIP/2.0
Via: SIP/2.0/UDP 192.168.2.8:5060;branch=z9hG4bK-f516699c
From: ;tag=f8fdd4d54e47c034o0
To: ;tag=324660314
Call-ID: af3b5629-f10e0ef0@192.168.2.8
CSeq: 101 ACK
Max-Forwards: 70
Contact:
User-Agent: Sipura/SPA2000-3.1.5
Content-Length: 0

[0:0]AUD Rel Call
CC:Failed
[0]On Hook
RSE_DEBUG: unref domain, s21.hkbntel.net
Sess Terminated
RSE_DEBUG: unref domain, s21.hkbntel.net
RSE_DEBUG: last unref for domain s21.hkbntel.net
Sess Terminated
CC:Clean Up
--- OBJ POOL STAT ---
OP:RTPRXB = 96 ( 96 192) OP:RTPREB = 40 ( 40 48)
OP:RTPTXB = 64 ( 64 108) OP:TIMEOU = 111 (120 40)
OP:SIPCOR = 0 ( 1 28) OP:SIPCTS = 32 ( 32 564)
OP:SIPSTS = 32 ( 32 3452) OP:SIPAUS = 6 ( 8 588)
OP:SIPDLG = 10 ( 10 140) OP:SIPSES = 12 ( 12 8184)
OP:SIPREG = 3 ( 4 244) OP:SIPLIN = 0 ( 2 128)
OP:STUNTS = 16 ( 16 68)
RSE_DEBUG: reference domain:s21.hkbntel.net
[0:5060]->203.80.89.135:5060
[0:5060]->203.80.89.135:5060
REGISTER sip:s2hkbntel.net SIP/2.0
Via: SIP/2.0/UDP 192.168.2.8:5060;branch=z9hG4bK-4f4b7b74
From: ;tag=65b11c9361af07d7o0
To:
Call-ID: 14269483-323e70a7@192.168.2.8
CSeq: 9 REGISTER
Max-Forwards: 70
Proxy-Authorization: Digest username="35961323",realm="Realm",nonce="MTEzNjA4OTE
xODMwOTE2ZTRiOTk2ZTY4MzBhODJjMDY3NmNmOTA3Njg5MGZk",uri="sip:s2hkbntel.net",algor
ithm=MD5,response="a7d5a2d8c5757bafe692ec7b44cd5aa1",qop=auth,nc=00000004,cnonce
="a1dbedcc"
Contact: ;expires=120
User-Agent: Sipura/SPA2000-3.1.5
Content-Length: 0
Allow: ACK, BYE, CANCEL, INFO, INVITE, NOTIFY, OPTIONS, REFER
· actions · 2005-Dec-31 11:37 pm ·
im_chandave
Premium Member
join:2005-07-28
Cleveland, OH

im_chandave

Premium Member

2006-Jan-1 1:49 am

  1. Don't try removing information unless you are sure what you removed is not relevant. You removed a lot of info in the Contact:, RESPONSES, and other things that makes it difficult to understand what is being responded by what.
  2. I haven't tried using HKBN on an i-Cable connection yet. An associate of mine attempted it but couldn't succeed. Of couse, she only tried once and didn't want to try to troubleshoot it.

In your syslog, I see:
  1. A SIP INVITE from your Sipura without any credentials being sent to HKBN
  2. What might be a SIP response of 100 Trying from HKBN
  3. What might be a SIP response of 200 OK from HKBN
  4. Your Sipura's ACK'ing the 200 response
  5. A failed establishment of audio channels since you told HKBN to use the IP address of 192.168.2.8 (your internal pre-NAT address) instead of your i-Cable address.
  6. A SIP REGISTER from your Sipura to HKBN with the proper credentials...but it appears cut-off and no response from HKBN was supplied in the syslog dump.
My suggestion:
  1. Turn on STUN support
  2. Enable NAT Mapping
If it still doesn't work, try to use the 2b softphone and see if it works. If it does, goto pa.2b.com.hk and reset your account. Try making a call with XTen/CounterPath's X-Lite to verify that a standard SIP client can work properly through i-Cable.

Also, if you do generate a syslog dump, please don't remove info from it. If you want to sanitize it:
  • Use 'X's for the digits of your phone number in the syslog dumps
  • Use 'Y's for the digits of the party you are calling or is calling you
  • Change the digits in "Digest username=" to 'X's
  • Leave the IP addresses in the "Via:" [or "v:" when receiving the SIP message from HKBN] lines. It very important for diagnostics. If you must sanitize it, just change the last digits of the "received=" IP address
  • Change the digits in the "From:" [or "f:" when receiving the SIP message from HKBN] to 'X's or 'Y's depending on if it's a call from you or going to you. Leave everything else in the line the same
  • Change the digits in the "To:" [or "t:" when receiving the SIP message from HKBN] to 'X's or 'Y's depending on if it's a call from you or going to you. Leave everything else in the line the same
  • Change the digits in the "Contact:" [or "m:" when receiving the SIP message from HKBN] to 'X's or 'Y's depending on if it's a call from you or going to you. Leave everything else in the line the same
  • Don't change the "Call-ID:" [or "i:" when receiving the SIP message from HKBN] line at all.

See ya...

d.c.
· actions · 2006-Jan-1 1:49 am ·
Forums → VOIP etc → VOIP → VOIP Tech Chat
« [Other] ubifone VOIP - http://www.ubifone.com • Cheapest DID ? »
This is a sub-selection from [Other] HKBN 2b PAP2 config