Displaying 4 results from an estimated 4 matches for "jrgvvvc".
2020 Sep 23
0
Negotiates g729 but RTP contains g711
...other than Asterisk, considering it's using iax2 in trunk mode.
We are running Asterisk 16.13.0, not sure what version the downstream is using.
caller -> upstream -> us -> downstream (IVR)
Herewith the SIP portion of the call, between upstream and us:
Available here: https://ibb.co/jRGvvVc
Wireshark unfortunately still cannot dissect iax2 trunk captures though, so I didn't know how to conclusively identify where this problem originates. I do however have a concern that the media we are receiving's packet size (74 bytes) indicates that it is most likely G729.
Herewith the I...
2020 Sep 22
2
Negotiates g729 but RTP contains g711
Hi,
We have a scenario where inbound calls from an upstream provider (chan_sip) sent downstream (chan_iax2) negotiates only g729 yet RTP media contains g711. Both the upstream and downstream trunks are limited to only offering g729 whilst the initial invite from our upstream provider offers both g711 and g729. Asterisk presumably simply forwards the media from iax2 trunk encapsulation to sip
2020 Sep 25
0
Negotiates g729 but RTP contains g711
...other than Asterisk, considering it's using iax2 in trunk mode.
We are running Asterisk 16.13.0, not sure what version the downstream is using.
caller -> upstream -> us -> downstream (IVR)
Herewith the SIP portion of the call, between upstream and us:
Available here: https://ibb.co/jRGvvVc
Wireshark unfortunately still cannot dissect iax2 trunk captures though, so I didn't know how to conclusively identify where this problem originates. I do however have a concern that the media we are receiving's packet size (74 bytes) indicates that it is most likely G729.
Herewith the I...
2020 Sep 24
2
Negotiates g729 but RTP contains g711
...other than Asterisk, considering it's using iax2 in trunk mode.
We are running Asterisk 16.13.0, not sure what version the downstream is using.
caller -> upstream -> us -> downstream (IVR)
Herewith the SIP portion of the call, between upstream and us:
Available here: https://ibb.co/jRGvvVc
Wireshark unfortunately still cannot dissect iax2 trunk captures though, so I didn't know how to conclusively identify where this problem originates. I do however have a concern that the media we are receiving's packet size (74 bytes) indicates that it is most likely G729.
Herewith the I...