Business Phone Systems

Forums Calendar Active Threads
Previous Thread
Next Thread
Print Thread
Rate Thread
SIP delay on start RTP
#439752 07/07/11 12:06 AM
Joined: Mar 2010
Posts: 86
Madrid
sbcsolutions Offline OP
Member
OP Offline
sbcsolutions
Member
Joined: Mar 2010
Posts: 86
Madrid
Hi all,
I realized there no audio in the first 4 seconds on SIP, then the conversation goes on correctly. Any idea how to solve this issue?

Regards.
Atcom VoIP Phones
VoIP Demo

Best VoIP Phones Canada

Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.

Re: SIP delay on start RTP
#439753 07/07/11 02:15 AM
Joined: Jun 2006
Posts: 2,986
Likes: 4
Brisbane, Australia
nameless Offline
Moderator-Samsung
*****
Offline
nameless
Moderator-Samsung
*****
Joined: Jun 2006
Posts: 2,986
Likes: 4
Brisbane, Australia
More information required.

System type and version
Handset type
Are there multiple MGI/OAS cards?
Ports forwarded correctly in the router?
Re: SIP delay on start RTP
#439754 07/07/11 03:37 AM
Joined: Mar 2010
Posts: 86
Madrid
sbcsolutions Offline OP
Member
OP Offline
sbcsolutions
Member
Joined: Mar 2010
Posts: 86
Madrid
This happens in almost all systems with SIP settings, but i'm referring to an OS7200 MCP v4.46a, OAS v2.01.
Re: SIP delay on start RTP
#439755 07/07/11 04:40 AM
Joined: Jun 2006
Posts: 2,986
Likes: 4
Brisbane, Australia
nameless Offline
Moderator-Samsung
*****
Offline
nameless
Moderator-Samsung
*****
Joined: Jun 2006
Posts: 2,986
Likes: 4
Brisbane, Australia
You need to get a trace from the system side to see if the RTP stream is getting to the OAS card, and what ports it is trying to reach.

If you can get your carrier to do a trace from their end at the same time and you can compare to see if the router is the issue or the system.
Re: SIP delay on start RTP
#439756 07/08/11 01:23 AM
Joined: Mar 2010
Posts: 86
Madrid
sbcsolutions Offline OP
Member
OP Offline
sbcsolutions
Member
Joined: Mar 2010
Posts: 86
Madrid
The problem is not with a SIP carrier. Is a connection to an IVR through SIP exten.
Re: SIP delay on start RTP
#439757 07/08/11 01:25 AM
Joined: Mar 2010
Posts: 86
Madrid
sbcsolutions Offline OP
Member
OP Offline
sbcsolutions
Member
Joined: Mar 2010
Posts: 86
Madrid
interface: any
filter: (ip) and ( port 5060 )
#
U 2011/06/21 13:33:45.254195 192.168.7.100:5060 -> 192.168.7.25:5060
INVITE sip:[email protected] SIP/2.0
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 1 INVITE
Via: SIP/2.0/UDP 192.168.7.100:5060;rport;branch=z9hG4bK-3dc8af4a-57ecbb44-17f5461
Max-Forwards: 70
Supported: 100rel,replaces
Reason: SIP; cause=1; text="0916326542"
Contact: <sip:[email protected]:5060>
Content-Type: application/SDP
Content-Length: 229

v=0
o=SAMSUNG_SIP_GATEWAY 1475132332 0 IN IP4 192.168.7.100
s=SIP_CALL
c=IN IP4 192.168.7.101
t=0 0
m=audio 30000 RTP/AVP 8 18 101
a=rtpmap:8 PCMA/8000
a=rtpmap:18 G729/8000
a=rtpmap:101 telephone-event/8000
a=sendrecv

#
U 2011/06/21 13:33:45.257186 192.168.7.25:5060 -> 192.168.7.100:5060
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 192.168.7.100:5060;branch=z9hG4bK-3dc8af4a-57ecbb44-17f5461;received=192.168.7.100;rport=5060
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>
Call-ID: [email protected]
CSeq: 1 INVITE
Server: Asterisk PBX 1.6.2.18
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Contact: <sip:[email protected]>
Content-Length: 0


#
U 2011/06/21 13:33:45.257244 192.168.7.25:5060 -> 192.168.7.100:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.7.100:5060;branch=z9hG4bK-3dc8af4a-57ecbb44-17f5461;received=192.168.7.100;rport=5060
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>;tag=as08b90a39
Call-ID: [email protected]
CSeq: 1 INVITE
Server: Asterisk PBX 1.6.2.18
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 235

v=0
o=root 252344691 252344691 IN IP4 192.168.7.25
s=Asterisk PBX 1.6.2.18
c=IN IP4 192.168.7.25
t=0 0
m=audio 15136 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U 2011/06/21 13:33:46.255826 192.168.7.25:5060 -> 192.168.7.100:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.7.100:5060;branch=z9hG4bK-3dc8af4a-57ecbb44-17f5461;received=192.168.7.100;rport=5060
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>;tag=as08b90a39
Call-ID: [email protected]
CSeq: 1 INVITE
Server: Asterisk PBX 1.6.2.18
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 235

v=0
o=root 252344691 252344691 IN IP4 192.168.7.25
s=Asterisk PBX 1.6.2.18
c=IN IP4 192.168.7.25
t=0 0
m=audio 15136 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U 2011/06/21 13:33:47.255704 192.168.7.25:5060 -> 192.168.7.100:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.7.100:5060;branch=z9hG4bK-3dc8af4a-57ecbb44-17f5461;received=192.168.7.100;rport=5060
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>;tag=as08b90a39
Call-ID: [email protected]
CSeq: 1 INVITE
Server: Asterisk PBX 1.6.2.18
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 235

v=0
o=root 252344691 252344691 IN IP4 192.168.7.25
s=Asterisk PBX 1.6.2.18
c=IN IP4 192.168.7.25
t=0 0
m=audio 15136 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U 2011/06/21 13:33:49.255532 192.168.7.25:5060 -> 192.168.7.100:5060
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.7.100:5060;branch=z9hG4bK-3dc8af4a-57ecbb44-17f5461;received=192.168.7.100;rport=5060
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>;tag=as08b90a39
Call-ID: [email protected]
CSeq: 1 INVITE
Server: Asterisk PBX 1.6.2.18
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO
Supported: replaces, timer
Contact: <sip:[email protected]>
Content-Type: application/sdp
Content-Length: 235

v=0
o=root 252344691 252344691 IN IP4 192.168.7.25
s=Asterisk PBX 1.6.2.18
c=IN IP4 192.168.7.25
t=0 0
m=audio 15136 RTP/AVP 8 101
a=rtpmap:8 PCMA/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=sendrecv

#
U 2011/06/21 13:33:49.559793 192.168.7.100:5060 -> 192.168.7.25:5060
ACK sip:[email protected] SIP/2.0
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>;tag=as08b90a39
Call-ID: [email protected]
CSeq: 1 ACK
Via: SIP/2.0/UDP 192.168.7.100:5060;rport;branch=z9hG4bK-3dc8af4e-57eccc8c-52f2ab86
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
Content-Length: 0


#
U 2011/06/21 13:33:52.202120 192.168.7.100:5060 -> 192.168.7.25:5060
ACK sip:[email protected] SIP/2.0
From: <sip:0916326542@192.168.7.100>;tag=c0a80764-13c4-3dc8af4a-57ecbb42-1e41fbc8
To: <sip:[email protected]>;tag=as08b90a39
Call-ID: [email protected]
CSeq: 1 ACK
Via: SIP/2.0/UDP 192.168.7.100:5060;rport;branch=z9hG4bK-3dc8af4e-57eccc8c-52f2ab86
Max-Forwards: 70
Contact: <sip:[email protected]:5060>
Content-Length: 0


exit
8 received, 0 dropped
Re: SIP delay on start RTP
#439758 07/08/11 02:48 AM
Joined: Mar 2010
Posts: 86
Madrid
sbcsolutions Offline OP
Member
OP Offline
sbcsolutions
Member
Joined: Mar 2010
Posts: 86
Madrid
both systems are in the same network.
Re: SIP delay on start RTP
#439759 07/08/11 05:39 AM
Joined: Jun 2006
Posts: 2,986
Likes: 4
Brisbane, Australia
nameless Offline
Moderator-Samsung
*****
Offline
nameless
Moderator-Samsung
*****
Joined: Jun 2006
Posts: 2,986
Likes: 4
Brisbane, Australia
If i read this correctly 192.168.7.100 is the MCP
192.168.7.101 is the OAS card and 192.168.7.25 is the asterisk box.

First packet the OS is making a call to the asterisk extension "produccion", this also tells the asterisk box to use PCMA (G.711 a-law) codec, and to send audio to 192.168.7.101 on port 30000.

Then we have a progress message from asterisk to os7200

Then we have a ok message from the asterisk box which also tells the OS7200 to send audio to 192.168.7.25 on port 15136 (PCMA Codec)

Etc

You have only captured the signalling which looks ok. Can you get another one with the audio packets as well?

Moderated by  nameless, pvj 

Link Copied to Clipboard
Forum Statistics
Forums84
Topics93,970
Posts637,430
Members49,704
Most Online5,661
May 23rd, 2018
Popular Topics(Views)
Today's Birthdays
DavidDC114, Deep (just a guy), Grokit01, QCIAthol
Newest Members
Acme Finishing, jim gray III, Merenth, Service Tech 911, Stephen A
49,703 Registered Users
Top Posters(30 Days)
Toner 12
mfecko 7
dexman 5
Who's Online Now
3 members (Memphisribs, adamsih300u, Professor Shadow), 78 guests, and 31 robots.
Key: Admin, Global Mod, Mod
Privacy Policy · Forum Rules · Mark All Read Contact Us · Forum Help · sundance-communications.com
Contact Us | Sponsored by Atcom: One of the best VoIP Phone Canada Suppliers for your business telephone system!| Terms of Service

Sundance Communications is not affiliated with any of the above manufacturers.
©Copyright Sundance Communications 1998-2023
Powered by UBB.threads™ PHP Forum Software 7.7.5