Firewall problem?? (using pfsense and Tony's QOS ini).
Sip Trunks work fine. and I have had sip:uri calls with no problems.
Using sipx 4.2.0, sipez .81
sipez developer was very responsive when I pointed out that I could not
make my test call (screaming monkies, ISN dialing: 1234*256.)
works now, but audio is a problem.
setup was easy (just keep in mind, the line AOR (identity) needs your
sipx user , not an alias sip string.
first time I used it, the echo portion of the test showed a 5 second
delay (on verizon 3g: EVDO, had 3 out of 5 bars)
subsequent calls, no echo at all. note, I did NOT use 'proxy'. that
seemed to eliminate audio even on first call.
Got full packet traces.
Interesting registration string:
Michael Scheidell<sip:[email protected]> Michael
Scheidell<sip:[email protected]:5060;LINEID=027652c13b72;x-sipX-nonat>
(name from their setup: DISPLAY NAME, sip:[email protected] from their AOR.)
softclient is NOT behind nat, and that IS the correct IP. Don't know
what LINEID is.
looks like it uses UDP by default.
has a button to allow you to 'register' to receive calls. (if you dial
outbound without registration, it will answer to the 401 and authenticate)
From invite packet: (I use ** as my ISN trunk code., I use 1234*256 as
my second regres test. first is to dial AA and try to transfer ).. that
actually failed. maybe it doesn't support RE-INVITE :-). person who
received the call saw my info on screen, answered, but status was 180,
ringing)
one thing I see, from sipx is asking for (something), and this says:
97.173.137.27 -> 192.168.0.2 RTP Unknown RTP version 0
Request-Line: INVITE sip:**1234*[email protected] SIP/2.0
Max-Forwards: 70
User-Agent: SIPez (Android)
Supported: replaces
Via: SIP/2.0/UDP 97.173.137.27;branch=z9hG4bK-e94abff3f229;rport
here is the invite after 407/authen:
Media Description, name and address (m): audio 9000 RTP/AVP 9 0 8 96
Media Type: audio
Media Port: 9000
Media Proto: RTP/AVP
Media Format: ITU-T G.722
Media Format: ITU-T G.711 PCMU
Media Format: ITU-T G.711 PCMA
Media Format: 96
Media Attribute (a): rtpmap:9 g722/8000/1
Media Attribute Fieldname: rtpmap
Media Format: 9
MIME Type: g722
Media Attribute (a): rtpmap:0 pcmu/8000/1
Media Attribute Fieldname: rtpmap
Media Format: 0
MIME Type: pcmu
(Mime type: pcmu.. vs PCMU, no case problem here, is there?
at recipeient end:
Media Description, name and address (m): audio 30498 RTP/AVP 0 8 96
Media Type: audio
Media Port: 30498
Media Proto: RTP/AVP
Media Format: ITU-T G.711 PCMU
Media Format: ITU-T G.711 PCMA
Media Format: 96
Connection Information (c): IN IP4 204.89.241.150
Connection Network Type: IN
Connection Address Type: IP4
Connection Address: 204.89.241.150
Media Attribute (a): rtpmap:0 PCMU/8000
Media Attribute Fieldname: rtpmap
Media Format: 0
MIME Type: PCMU
Media Attribute (a): rtpmap:8 PCMA/8000
Media Attribute Fieldname: rtpmap
Media Format: 8
MIME Type: PCMA
other: calling AA (supports G.722, actually sounds good)
2010-09-24 10:55:43.800045 192.168.0.2 -> 97.173.137.27 SIP Request:
REFER sip:[email protected]:5060;x-sipX-nonat
2010-09-24 10:55:43.826035 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=349, Time=898280047
2010-09-24 10:55:43.833211 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=350, Time=898280207
2010-09-24 10:55:43.880045 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=351, Time=898280367
2010-09-24 10:55:43.886752 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=352, Time=898280527
2010-09-24 10:55:43.925614 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=353, Time=898280687
2010-09-24 10:55:43.958703 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=354, Time=898280847
2010-09-24 10:55:43.965869 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=355, Time=898281007
2010-09-24 10:55:43.999622 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=356, Time=898281167
2010-09-24 10:55:44.005084 192.168.0.2 -> 97.173.137.27 SIP Request:
REFER sip:[email protected]:5060;x-sipX-nonat
2010-09-24 10:55:44.006135 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=357, Time=898281327
2010-09-24 10:55:44.032738 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=358, Time=898281487
2010-09-24 10:55:44.039752 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=359, Time=898281647
2010-09-24 10:55:44.073220 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=360, Time=898281807
2010-09-24 10:55:44.080362 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=361, Time=898281967
2010-09-24 10:55:44.105778 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=362, Time=898282127
2010-09-24 10:55:44.139089 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=363, Time=898282287
2010-09-24 10:55:44.171547 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=364, Time=898282447
2010-09-24 10:55:44.179580 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=365, Time=898282607
2010-09-24 10:55:44.211620 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=366, Time=898282767
2010-09-24 10:55:44.218937 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=367, Time=898282927
2010-09-24 10:55:44.245707 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=368, Time=898283087
2010-09-24 10:55:44.253114 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=369, Time=898283247
2010-09-24 10:55:44.259773 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=370, Time=898283407
2010-09-24 10:55:44.285290 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=371, Time=898283567
2010-09-24 10:55:44.299899 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=372, Time=898283727
2010-09-24 10:55:44.324716 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=373, Time=898283887
2010-09-24 10:55:44.338793 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=374, Time=898284047
2010-09-24 10:55:44.365644 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=375, Time=898284207
2010-09-24 10:55:44.373411 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=376, Time=898284367
2010-09-24 10:55:44.405407 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=377, Time=898284527
2010-09-24 10:55:44.408042 192.168.0.2 -> 97.173.137.27 SIP Request:
REFER sip:[email protected]:5060;x-sipX-nonat
2010-09-24 10:55:44.412009 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=378, Time=898284687
2010-09-24 10:55:44.446539 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=379, Time=898284847
2010-09-24 10:55:44.479395 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=380, Time=898285007
2010-09-24 10:55:44.486405 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=381, Time=898285167
2010-09-24 10:55:44.493270 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=382, Time=898285327
2010-09-24 10:55:44.525619 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=383, Time=898285487
2010-09-24 10:55:44.531782 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=384, Time=898285647
2010-09-24 10:55:44.559155 97.173.137.27 -> 192.168.0.2 RTP PT=ITU-T
G.722, SSRC=0x4C9087FD, Seq=385, Time=898285807
2010-09-24 10:55:44.793376 97.173.137.27 -> 192.168.0.2 SIP Status:
202 Accepted
2010-09-24 10:55:44.959615 97.173.137.27 -> 192.168.0.2 SIP/SDP
Request: INVITE sip:[email protected]:15060;transport=udp, with session
description
2010-09-24 10:55:44.961443 192.168.0.2 -> 97.173.137.27 SIP Status:
100 Trying
2010-09-24 10:55:44.971237 192.168.0.2 -> 97.173.137.27 SIP/SDP
Status: 200 OK, with session description
2010-09-24 10:55:45.272227 97.173.137.27 -> 192.168.0.2 SIP Request:
ACK sip:[email protected]:15060;transport=udp
2010-09-24 10:55:45.272955 97.173.137.27 -> 192.168.0.2 RTP Unknown
RTP version 0
2010-09-24 10:55:45.279436 97.173.137.27 -> 192.168.0.2 RTCP Source
port: 9001 Destination port: 30499
2010-09-24 10:55:45.526968 97.173.137.27 -> 192.168.0.2 SIP/SDP
Request: INVITE sip:[email protected], with session description
2010-09-24 10:55:45.528701 192.168.0.2 -> 97.173.137.27 SIP Status:
100 Trying
2010-09-24 10:55:45.944903 192.168.0.2 -> 97.173.137.27 SIP Status:
180 Ringing
2010-09-24 10:55:46.278355 97.173.137.27 -> 192.168.0.2 SIP/sipfrag
Request: NOTIFY sip:[email protected]:15060;transport=udp;x-sipX-nonat,
with Sipfrag(SIP/2.0 180 Ringing...)
2010-09-24 10:55:46.283534 192.168.0.2 -> 97.173.137.27 SIP Status:
200 OK
never connects, I stop hearing audio as soon as it xfers. no MOH, no
nithing.
--
Michael Scheidell, CTO
o: 561-999-5000
d: 561-948-2259
ISN: 1259*1300
> *| *SECNAP Network Security Corporation
* Certified SNORT Integrator
* 2008-9 Hot Company Award Winner, World Executive Alliance
* Five-Star Partner Program 2009, VARBusiness
* Best in Email Security,2010: Network Products Guide
* King of Spam Filters, SC Magazine 2008
______________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.secnap.com/products/spammertrap/
______________________________________________________________________
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/
