search for: as40fe2614

Displaying 4 results from an estimated 4 matches for "as40fe2614".

Negotiates g729 but RTP contains g711
2020 Sep 24
2
Negotiates g729 but RTP contains g711
...x) but then transmits g711a media to +27888888888 (chan_sip). Herewith the scrubbed logging with SIP debug: [2020-09-19 23:42:19] VERBOSE[2637] chan_sip.c: <--- SIP read from UDP:41.11.11.12:5060 ---> INVITE sip:0100000000 at 52.22.22.22:5160 SIP/2.0 Record-Route: <sip:41.11.11.12;lr;ftag=as40fe2614> Via: SIP/2.0/UDP 41.11.11.12:5060;branch=z9hG4bK4df7.5bc77035.0 Via: SIP/2.0/UDP 41.11.11.11:5070;received=41.11.11.11;branch=z9hG4bK0cb77ea3;rport=5070 From: "+27888888888" <sip:+27888888888 at 41.11.11.11:5070>;tag=as40fe2614 To: <sip:0100000000 at 52.22.22.22:5160> Cont...
Negotiates g729 but RTP contains g711
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
Negotiates g729 but RTP contains g711
2020 Sep 25
0
Negotiates g729 but RTP contains g711
...88888 (chan_sip). Herewith the scrubbed and reduced dialogues, full details are available in the JIRA case: [2020-09-19 23:42:19] VERBOSE[2637] chan_sip.c: <--- SIP read from UDP:41.11.11.12:5060 ---> INVITE sip:0100000000 at 52.22.22.22:5160 SIP/2.0 Record-Route: <sip:41.11.11.12;lr;ftag=as40fe2614> Via: SIP/2.0/UDP 41.11.11.12:5060;branch=z9hG4bK4df7.5bc77035.0 Via: SIP/2.0/UDP 41.11.11.11:5070;received=41.11.11.11;branch=z9hG4bK0cb77ea3;rport=5070 From: "+27888888888" <sip:+27888888888 at 41.11.11.11:5070>;tag=as40fe2614 To: <sip:0100000000 at 52.22.22.22:5160> Cont...
Negotiates g729 but RTP contains g711
2020 Sep 25
0
Negotiates g729 but RTP contains g711
...88888 (chan_sip). Herewith the scrubbed and reduced dialogues, full details are available in the JIRA case: [2020-09-19 23:42:19] VERBOSE[2637] chan_sip.c: <--- SIP read from UDP:41.11.11.12:5060 ---> INVITE sip:0100000000 at 52.22.22.22:5160 SIP/2.0 Record-Route: <sip:41.11.11.12;lr;ftag=as40fe2614> Via: SIP/2.0/UDP 41.11.11.12:5060;branch=z9hG4bK4df7.5bc77035.0 Via: SIP/2.0/UDP 41.11.11.11:5070;received=41.11.11.11;branch=z9hG4bK0cb77ea3;rport=5070 From: "+27888888888" <sip:+27888888888 at 41.11.11.11:5070>;tag=as40fe2614 To: <sip:0100000000 at 52.22.22.22:5160> Cont...