we are running a toll bypass scenario with two Meridian PBX's connected over a link using QSIG signalling. While trouble shooting a problem I noticed the following during a call set up with the 'sh call active voice' command
Total call-legs: 2
AA7 : 60964970hs.1 +-1 pid:5 Answer 536 connected
dur 00:00:00 tx:0/0 rx:0/0
IP 172.16.5.2:17322 rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 pre-ietf
AA7 : 60965288hs.1 +-1 pid:9 Originate 90191262 connecting
dur 00:00:00 tx:0/0 rx:0/0
Tele 1/0:15 (3474): tx:0/0/0ms None noise:0 acom:0 i/0:0/0 dBm
Total call-legs: 2
AA7 : 60964970hs.1 +-1 pid:5 Answer 536 connected
dur 00:00:00 tx:0/0 rx:0/0
IP 172.16.5.2:17322 rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g729r8 pre-ietf
AA7 : 60965288hs.1 +-1 pid:9 Originate 90191262 connecting
dur 00:00:00 tx:0/0 rx:0/0
Tele 1/0:15 (3474): tx:0/0/0ms None noise:0 acom:0 i/0:0/0 dBm
Total call-legs: 2
AA7 : 60964970hs.1 +1665 pid:5 Answer 536 active
dur 00:00:03 tx:0/0 rx:0/0
IP 172.16.5.2:17322 rtt:0ms pl:0/0ms lost:0/0/0 delay:0/0/0ms g711alaw
AA7 : 60965288hs.1 +1347 pid:9 Originate 90191262 active
dur 00:00:03 tx:185/29361 rx:116/18082
Tele 1/0:15 (3474): tx:3800/2280/0ms g711alaw noise:-67 acom:2 i/0:-63/-37 dBm
It shows the call being set up with the g729r8 pre-ietf codec despite the config dictating g711a.
Does anyone know if this is normal??
