No Voice

Discuss any topic about Brekeke SIP Server.

Moderator: Brekeke Support Team

Post Reply
samyray
Posts: 2
Joined: Mon Sep 27, 2010 4:18 am
Location: Ukraine

No Voice

Post by samyray »

1. Brekeke Product Name and version: Brekeke SIP 2.4.7

2. Java version:

3. OS type and the version: Linux Ubuntu

4. UA (phone), gateway or other hardware/software involved:

5. Select your network pattern from http://www.brekeke-sip.com/bbs/network/ ... terns.html :

6. Your problem:
We are using our local SIP provider and we followed the manual instructions and we can call/receive calls from one type of numbers.
But when we are trying to call to our GSM providers,all call sessions are on 'accepted' status and there is no voice.
Also this sessions don't close if we hang up the phone.
Can somebody help me?
Top
voipwell.com
Posts: 528
Joined: Tue Sep 20, 2005 9:10 am
Location: Tannersville, Pennsylvania

Post by voipwell.com »

Can you run a packet trace with wireshark to see the sip responses?
Top
Harold
Posts: 289
Joined: Sun Sep 21, 2008 10:31 pm
Location: Japan

Post by Harold »

samyray,

what kind of sip client are you using??
if the problem happens only with the GSM provider, the cause will be in them.

the 'accepted' means that the SIP server received "200 OK" but it doesn't receive "ACK" yet which should be sent from the caller.
Top
samyray
Posts: 2
Joined: Mon Sep 27, 2010 4:18 am
Location: Ukraine

Post by samyray »

Hello
Here is what I have got using this command on linux server:
tcpdump -c 200 -pi eth0 -s0 -w sipdump host 62.221.34.30 and udp port 5060
Where 62.221.34.30 is my SIP provider
First is call with voice,and second is without voice
About SIP client - I am using Grandstream BudgeTone-200 and DrayTek VigorPhone 350
And I have this problem with all GSM providers.
Voice On

�ò���䞡L�������k*���E�@@���>�"��~(�INVITE sip:+380444823220@62.221.34.30:2004 SIP/2.0
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK307d01f940ac5fb16496-cd3c2421-3f908217
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=be881d553p
To: <sip:+380444823220@62.221.34.30:2004>
Max-Forwards: 18
Contact: <sip:+380445037888@212.90.189.112:5060>
Call-ID: b2787d77-bcbc2214-44bfe84d-346f3ea3@212.90.189.112
User-Agent: Brekeke PBX
CSeq: 1 INVITE
Allow: INVITE,ACK,BYE,CANCEL,INFO,MESSAGE,REFER,NOTIFY,SUBSCRIBE,UPDATE,PRACK
Content-Type: application/sdp
Content-Length: 313

v=0
o=brekeke 1022 0 IN IP4 212.90.189.112
s=-
c=IN IP4 212.90.189.112
t=0 0
m=audio 10014 RTP/AVP 18 98 0 101
a=sendrecv
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=ptime:20
a=rtpmap:98 iLBC/8000
a=fmtp:98 mode=30
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
䞡Loe�����$���kE�@��<>�"�������ySIP/2.0 100 Trying
Call-ID: b2787d77-bcbc2214-44bfe84d-346f3ea3@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=be881d553p
To: <sip:+380444823220@62.221.34.30:2004>;tag=9308960220998424343
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK307d01f940ac5fb16496-cd3c2421-3f908217
Supported: timer,100rel
Content-Length: 0

垡L"�99���$���kE+@�˪>�"������SIP/2.0 180 Ringing
Call-ID: b2787d77-bcbc2214-44bfe84d-346f3ea3@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=be881d553p
To: <sip:+380444823220@62.221.34.30:2004>;tag=9308960220998424343
Content-Type: application/sdp
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK307d01f940ac5fb16496-cd3c2421-3f908217
Contact: <sip:+380444823220@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 305

v=0
o=MG4000|2.0 19589 19589 IN IP4 62.221.34.18
s=-
c=IN IP4 62.221.34.18
t=0 0
m=audio 51298 RTP/AVP 18 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=fmtp:18 annexb=no
a=ptime:20
a=X-vrzcap:vbd Ver=0 Mode=FaxPr ModemRtpRed=0
a=X-vrzcap:identification bin=DSR2814l Prot=mgcp App=MG
YY���$���kEK@��j>�"�����7<�SIP/2.0 200 OK
Call-ID: b2787d77-bcbc2214-44bfe84d-346f3ea3@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=be881d553p
To: <sip:+380444823220@62.221.34.30:2004>;tag=9308960220998424343
Content-Type: application/sdp
Session-Expires: 3600;refresher=uas
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK307d01f940ac5fb16496-cd3c2421-3f908217
Contact: <sip:+380444823220@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 305

v=0
o=MG4000|2.0 19589 19589 IN IP4 62.221.34.18
s=-
c=IN IP4 62.221.34.18
t=0 0
m=audio 51298 RTP/AVP 18 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=fmtp:18 annexb=no
a=ptime:20
a=X-vrzcap:vbd Ver=0 Mode=FaxPr ModemRtpRed=0
a=X-vrzcap:identification bin=DSR2814l Prot=mgcp App=MG
鞡LF���k*���E@@����>�"���'LACK sip:+380444823220@62.221.34.30:2004;user=phone SIP/2.0
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK88ba33d6d3b084b16496-cd3c2421-8c084a74
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=be881d553p
To: <sip:+380444823220@62.221.34.30:2004>;tag=9308960220998424343
Max-Forwards: 18
Contact: <sip:+380445037888@212.90.189.112:5060>
Call-ID: b2787d77-bcbc2214-44bfe84d-346f3ea3@212.90.189.112
User-Agent: Brekeke PBX
CSeq: 1 ACK
Content-Length: 0

���L!������$���kE֏@@�̍>�"�����—�BYE sip:+380445037888@212.90.189.112:5060 SIP/2.0
Call-ID: b2787d77-bcbc2214-44bfe84d-346f3ea3@212.90.189.112
From: <sip:+380444823220@62.221.34.30:2004>;tag=9308960220998424343
To: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=be881d553p
CSeq: 1 BYE
Via: SIP/2.0/UDP 62.221.34.30:2004;branch=z9hG4bK-8130120000da5717-a2001b5-2
Supported: timer,100rel
Max-Forwards: 70
User-Agent: VCS 5.8.2.22-02
Content-Length: 0

���L������k*���Eu@@,���>�"��a&�SIP/2.0 200 OK
Via: SIP/2.0/UDP 62.221.34.30:2004;branch=z9hG4bK-8130120000da5717-a2001b5-2;rport=2004
From: <sip:+380444823220@62.221.34.30:2004>;tag=9308960220998424343
To: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=be881d553p
Call-ID: b2787d77-bcbc2214-44bfe84d-346f3ea3@212.90.189.112
CSeq: 1 BYE
Content-Length: 0

Voice Off

��v��L��
[[���k*���EM@@T���>�"��9(�INVITE sip:+380977866590@62.221.34.30:2004 SIP/2.0
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>
Max-Forwards: 18
Contact: <sip:+380445037888@212.90.189.112:5060>
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
User-Agent: Brekeke PBX
CSeq: 1 INVITE
Allow: INVITE,ACK,BYE,CANCEL,INFO,MESSAGE,REFER,NOTIFY,SUBSCRIBE,UPDATE,PRACK
Content-Type: application/sdp
Content-Length: 245

v=0
o=brekeke 1016 0 IN IP4 212.90.189.112
s=-
c=IN IP4 212.90.189.112
t=0 0
m=audio 10006 RTP/AVP 8 0 101
a=sendrecv
a=rtpmap:8 PCMA/8000
a=ptime:20
a=rtpmap:0 PCMU/8000
a=ptime:20
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
�����$���kE���@��z>�"��������SIP/2.0 100 Trying
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
Supported: timer,100rel
Content-Length: 0

y��L/������$���kEጔ@��.>�"�����͍hSIP/2.0 183 Session Progress
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
Contact: <sip:+380977866590@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 0

y��LQ�++���$���kE��@���>�"����� �<SIP/2.0 183 Session Progress
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
Content-Type: application/sdp
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
Contact: <sip:+380977866590@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 283

v=0
o=MG4000|2.0 42769 42769 IN IP4 62.221.34.18
s=-
c=IN IP4 62.221.34.18
t=0 0
m=audio 57658 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=X-vrzcap:vbd Ver=0 Mode=FaxPr ModemRtpRed=0
a=X-vrzcap:identification bin=DSR2814l Prot=mgcp App=MG
z��L8�""���$���kE��@���>�"�����<�SIP/2.0 180 Ringing
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
Content-Type: application/sdp
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
Contact: <sip:+380977866590@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 283

v=0
o=MG4000|2.0 42769 42769 IN IP4 62.221.34.18
s=-
c=IN IP4 62.221.34.18
t=0 0
m=audio 57658 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=X-vrzcap:vbd Ver=0 Mode=FaxPr ModemRtpRed=0
a=X-vrzcap:identification bin=DSR2814l Prot=mgcp App=MG
|��L� BB���$���kE4��@���>�"����� ;�SIP/2.0 200 OK
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
Content-Type: application/sdp
Session-Expires: 3600;refresher=uas
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
Contact: <sip:+380977866590@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 283

v=0
o=MG4000|2.0 42769 42769 IN IP4 62.221.34.18
s=-
c=IN IP4 62.221.34.18
t=0 0
m=audio 57658 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=X-vrzcap:vbd Ver=0 Mode=FaxPr ModemRtpRed=0
a=X-vrzcap:identification bin=DSR2814l Prot=mgcp App=MG
}��L
�BB���$���kE4��@���>�"����� ;�SIP/2.0 200 OK
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
Content-Type: application/sdp
Session-Expires: 3600;refresher=uas
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
Contact: <sip:+380977866590@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 283

v=0
o=MG4000|2.0 42769 42769 IN IP4 62.221.34.18
s=-
c=IN IP4 62.221.34.18
t=0 0
m=audio 57658 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=X-vrzcap:vbd Ver=0 Mode=FaxPr ModemRtpRed=0
a=X-vrzcap:identification bin=DSR2814l Prot=mgcp App=MG
~��L�dBB���$���kE4��@�͵>�"����� ;�SIP/2.0 200 OK
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
Content-Type: application/sdp
Session-Expires: 3600;refresher=uas
CSeq: 1 INVITE
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK1b480e0d6ddfacb16496-b44a1375-3ff982ba
Contact: <sip:+380977866590@62.221.34.30:2004;user=phone>
Supported: timer,100rel
Content-Length: 283

v=0
o=MG4000|2.0 42769 42769 IN IP4 62.221.34.18
s=-
c=IN IP4 62.221.34.18
t=0 0
m=audio 57658 RTP/AVP 8 101
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=X-vrzcap:vbd Ver=0 Mode=FaxPr ModemRtpRed=0
a=X-vrzcap:identification bin=DSR2814l Prot=mgcp App=MG
~��L�� �����$���kEՌ�@��>�"������Y�BYE sip:+380445037888@212.90.189.112:5060 SIP/2.0
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
From: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
To: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
CSeq: 1 BYE
Via: SIP/2.0/UDP 62.221.34.30:2004;branch=z9hG4bK-8130120000da558a-a2001b5-2
Supported: timer,100rel
Max-Forwards: 70
User-Agent: VCS 5.8.2.22-02
Content-Length: 0

~��L�� �����k*���Et@@-���>�"��`&�SIP/2.0 200 OK
Via: SIP/2.0/UDP 62.221.34.30:2004;branch=z9hG4bK-8130120000da558a-a2001b5-2;rport=2004
From: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
To: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
CSeq: 1 BYE
Content-Length: 0

~��LL� ���k*���E@@����>�"���'KACK sip:+380977866590@62.221.34.30:2004;user=phone SIP/2.0
Via: SIP/2.0/UDP 212.90.189.112:5060;rport;branch=z9hG4bK13ab5af0934a0fb16496-b44a1375-1a981100
From: "+380445037888" <sip:+380445037888@212.90.189.112:5060>;tag=b7e3ad938p
To: <sip:+380977866590@62.221.34.30:2004>;tag=9308960220998423946
Max-Forwards: 18
Contact: <sip:+380445037888@212.90.189.112:5060>
Call-ID: f1466422-ea0bf289-12feeb38-2ae418e@212.90.189.112
User-Agent: Brekeke PBX
CSeq: 1 ACK
Content-Length: 0

Top
Harold
Posts: 289
Joined: Sun Sep 21, 2008 10:31 pm
Location: Japan

Post by Harold »

If you bypass the PBX, does the same issue happen?
http://wiki.brekeke.com/wiki/How-to-Bridge-Brekeke-PBX
Top
Post Reply

Return to “Brekeke SIP Server Forum”