1-way audip

[pbxuser911]

here is the logfile, what does it look like the issue is here? the PBX is trying to send G729? i have G711 on the list first

 

 

[5] 2009/08/29 23:28:39: Identify trunk (domain name match) 168

[6] 2009/08/29 23:28:39: Sending RTP for 5be1ebd3-e90c4e0e-e5edfb21@192.168.1.103#f130d979e7 to 192.168.1.103:2254

[9] 2009/08/29 23:28:39: Dialplan: Evaluating !^([0-9]{10})@.*!sip:\1@\r;user=phone!i against 2125551212@sip.mycompany.com

[5] 2009/08/29 23:28:39: Dialplan default dialplan: Match 2125551212@sip.mycompany.com to <sip:2125551212@66.33.157.119;user=phone> on trunk Net2Phone_SIPGW_O_01

[8] 2009/08/29 23:28:39: Play audio_moh/noise.wav

[6] 2009/08/29 23:28:39: Send codec pcmu/8000

[6] 2009/08/29 23:28:39: Sending RTP for 5be1ebd3-e90c4e0e-e5edfb21@192.168.1.103#f130d979e7 to 69.248.96.205:2254

[6] 2009/08/29 23:28:41: Sending RTP for e76db31a@pbx#1878503665 to 169.132.188.43:25886

[6] 2009/08/29 23:28:41: Send codec=g729/8000 after answer

[7] 2009/08/29 23:28:41: e76db31a@pbx#1878503665: RTP pass-through mode

[7] 2009/08/29 23:28:41: 5be1ebd3-e90c4e0e-e5edfb21@192.168.1.103#f130d979e7: RTP pass-through mode

[7] 2009/08/29 23:28:41: Cannot pass through on 5be1ebd3-e90c4e0e-e5edfb21@192.168.1.103#f130d979e7, falling back to transcoding

[pbxuser911]

on the actuall trunk i change the codec to use (override codec prefrences) G711 and it works fine

why doesnt it to begin with use G711? instead it looks like its trying to use G729, and maybe my phone doesnt support G729 thats why i cant hear anything?

[Vodia PBX]

on the actuall trunk i change the codec to use (override codec prefrences) G711 and it works fine

why doesnt it to begin with use G711? instead it looks like its trying to use G729, and maybe my phone doesnt support G729 thats why i cant hear anything?

 

Try to lock the codec down. Maybe the provider is not able to deal with asymetric codecs.

[pbxuser911]

this is how i have it set up

 

i have the same setting on all other trunks and it works fine, what do you suggest i do?

i want a solution thats going to work fine all over, i dont want based on certain phones to have to change anything

and also for some reason when i call from a linksys phone it works fine, but when calling from a polycom phone it doesnt work

 

is it possible the polycom phones first try to use G729?

 

below is logfile of 2 calls, 1 is making a cal form a polycom that had 1-way audio, and 1 is a linksys that worked fine

 

[5] 2009/08/30 15:51:11: Identify trunk (domain name match) 168

[8] 2009/08/30 15:51:11: Using outbound proxy sip:69.248.96.205:1029;transport=udp because UDP packet source did not match the via header

[8] 2009/08/30 15:51:11: Tagging request with existing tag

[6] 2009/08/30 15:51:11: Sending RTP for 9e09b11b-d900d596-209216e9@192.168.1.103#c448c6a60d to 192.168.1.103:2240

[8] 2009/08/30 15:51:11: Play audio_moh/noise.wav

[6] 2009/08/30 15:51:11: Send codec pcmu/8000

[8] 2009/08/30 15:51:11: Removing registration d56bb2f3-b8c4a585-a87d520a@192.168.1.100

[8] 2009/08/30 15:51:11: Removing registration d5bb586d-1326fea3-41569b5a@192.168.1.97

[6] 2009/08/30 15:51:11: Sending RTP for 9e09b11b-d900d596-209216e9@192.168.1.103#c448c6a60d to 69.248.96.205:2240

[8] 2009/08/30 15:51:11: Removing registration 5858a61a-c5803c94-58dc42db@192.168.1.18

[8] 2009/08/30 15:51:11: Removing registration 3c5a1a42-3ae41e28-689c16a9@192.168.1.101

[8] 2009/08/30 15:51:12: Removing registration 70968ebd-42b3d2e3-a8a98756@10.10.0.108

[8] 2009/08/30 15:51:12: Removing registration 53c55efa-2989c403-81c0490@192.168.8.2

[8] 2009/08/30 15:51:12: Removing registration 60df8059-ee5ff7af-1104651e@192.168.2.131

[8] 2009/08/30 15:51:12: Removing registration c8780df7-fa2caabd-af615ebc@192.168.168.103

[8] 2009/08/30 15:51:12: Play recordings/personal1284-1.wav audio_en/mb_leave_msg_after_tone.wav audio_moh/mb_beep.wav

[7] 2009/08/30 15:51:12: Call 7b88f155@pbx#2061564575: Clear last request

[7] 2009/08/30 15:51:13: Call 7b88f155@pbx#2061564575: Clear last INVITE

[5] 2009/08/30 15:51:13: INVITE Response 487 Request Cancelled: Terminate 7b88f155@pbx

[7] 2009/08/30 15:51:13: Other Ports: 9

[7] 2009/08/30 15:51:13: Call Port: 14e0eff6@pbx#160929904

[7] 2009/08/30 15:51:13: Call Port: 4D5A6D5B@sip10.siptrunk.com#3f6a5f785c

[7] 2009/08/30 15:51:13: Call Port: 74ba8daa@pbx#1444840570

[7] 2009/08/30 15:51:13: Call Port: 8694f9ea@pbx#1209736123

[7] 2009/08/30 15:51:13: Call Port: 9723879b-654fb478@localhost#af51c45ece

[7] 2009/08/30 15:51:13: Call Port: 9e09b11b-d900d596-209216e9@192.168.1.103#c448c6a60d

[7] 2009/08/30 15:51:13: Call Port: D8916B48@sip10.siptrunk.com#ad806b5e6e

[7] 2009/08/30 15:51:13: Call Port: a4d2d529-40c61989@192.168.1.2#d7d50a349a

[7] 2009/08/30 15:51:13: Call Port: f95c0af0@pbx#1105414618

[8] 2009/08/30 15:51:13: Removing registration 59a2981-f20849b3-58002bec@192.168.1.2

[6] 2009/08/30 15:51:13: Sending RTP for 14e0eff6@pbx#160929904 to 169.132.188.44:17532

[8] 2009/08/30 15:51:13: Removing registration 1c1a9426-b7aa21d4-1f82917b@192.168.1.100

[8] 2009/08/30 15:51:13: Removing registration f6c3136d-6622ff4f-cf8b936e@192.168.168.104

[8] 2009/08/30 15:51:13: Removing registration b9e543f4-ef7e41fe-18b3e697@192.168.3.178

[6] 2009/08/30 15:51:13: Send codec=g729/8000 after answer

[7] 2009/08/30 15:51:13: 14e0eff6@pbx#160929904: RTP pass-through mode

[7] 2009/08/30 15:51:13: 9e09b11b-d900d596-209216e9@192.168.1.103#c448c6a60d: RTP pass-through mode

[7] 2009/08/30 15:51:13: Cannot pass through on 9e09b11b-d900d596-209216e9@192.168.1.103#c448c6a60d, falling back to transcoding

[8] 2009/08/30 15:51:13: Removing registration 58f77c14-18399a36-dfcc0bb9@192.168.15.100

[8] 2009/08/30 15:51:13: Removing registration 23737307-d8d90d09-5e0ef554@192.168.1.24

[8] 2009/08/30 15:51:13: Removing registration 535a5129-d80b550b-e4b30ebe@192.168.1.24

[8] 2009/08/30 15:51:13: Removing registration 3cf268df-a8b75a99-996fbd4a@192.168.1.45

[8] 2009/08/30 15:51:13: Removing registration 96d80828-eb9c83a6-ba0ec4a5@71.249.202.7

[8] 2009/08/30 15:51:13: Removing registration 1391b06e-b9fe2fc4-3b817933@192.168.1.10

[8] 2009/08/30 15:51:13: Removing registration 76cb102a-f817d718-22698a07@192.168.1.102

[8] 2009/08/30 15:51:13: Removing registration ef00dc74-6f7f174a-a84e1d73@192.168.1.103

[8] 2009/08/30 15:51:13: Removing registration a282a46-f9fc9a58-63446353@192.168.1.24

[8] 2009/08/30 15:51:14: Removing registration b74ca541-4271d4cf-7c95baea@192.168.1.103

[7] 2009/08/30 15:51:14: Call 14e0eff6@pbx#160929904: Clear last request

[7] 2009/08/30 15:51:14: Call 14e0eff6@pbx#160929904: Clear last INVITE

[5] 2009/08/30 15:51:14: INVITE Response 487 Request Cancelled: Terminate 14e0eff6@pbx

[7] 2009/08/30 15:51:14: 9e09b11b-d900d596-209216e9@192.168.1.103#c448c6a60d: Media-aware pass-through mode

[7] 2009/08/30 15:51:14: Other Ports: 8

[7] 2009/08/30 15:51:14: Call Port: 4D5A6D5B@sip10.siptrunk.com#3f6a5f785c

[7] 2009/08/30 15:51:14: Call Port: 74ba8daa@pbx#1444840570

[7] 2009/08/30 15:51:14: Call Port: 8694f9ea@pbx#1209736123

[7] 2009/08/30 15:51:14: Call Port: 9723879b-654fb478@localhost#af51c45ece

[7] 2009/08/30 15:51:14: Call Port: 9e09b11b-d900d596-209216e9@192.168.1.103#c448c6a60d

[7] 2009/08/30 15:51:14: Call Port: D8916B48@sip10.siptrunk.com#ad806b5e6e

[7] 2009/08/30 15:51:14: Call Port: a4d2d529-40c61989@192.168.1.2#d7d50a349a

[7] 2009/08/30 15:51:14: Call Port: f95c0af0@pbx#1105414618

[7] 2009/08/30 15:51:14: Other Ports: 7

[7] 2009/08/30 15:51:14: Call Port: 4D5A6D5B@sip10.siptrunk.com#3f6a5f785c

[7] 2009/08/30 15:51:14: Call Port: 74ba8daa@pbx#1444840570

[7] 2009/08/30 15:51:14: Call Port: 8694f9ea@pbx#1209736123

[7] 2009/08/30 15:51:14: Call Port: 9723879b-654fb478@localhost#af51c45ece

[7] 2009/08/30 15:51:14: Call Port: D8916B48@sip10.siptrunk.com#ad806b5e6e

[7] 2009/08/30 15:51:14: Call Port: a4d2d529-40c61989@192.168.1.2#d7d50a349a

[7] 2009/08/30 15:51:14: Call Port: f95c0af0@pbx#1105414618

[8] 2009/08/30 15:51:14: Removing registration ca41d359-2205ec17-9c7d4214@192.168.7.79

[8] 2009/08/30 15:51:14: Removing registration b199631f-5eccf4d5-b93febe8@192.168.1.104

[8] 2009/08/30 15:51:14: Removing registration e243186e-8d598ac-432487f1@192.168.1.125

[8] 2009/08/30 15:51:14: Removing registration f39d8852-b2104c78-4d340e71@192.168.1.112

[8] 2009/08/30 15:51:14: Removing registration dc69fca0-65831b6a-261760ff@192.168.1.9

[8] 2009/08/30 15:51:14: Removing registration bddc0331-d18446c7-f2186d86@10.10.0.107

[8] 2009/08/30 15:51:15: Removing registration 4ccc557c-9c8a570e-12a2b711@71.249.202.7

[8] 2009/08/30 15:51:15: Removing registration afb40349-16c68ac3-8a42d5a@192.168.7.147

[8] 2009/08/30 15:51:15: Removing registration ac23c4-e56616f6-338ab155@24.189.101.131

[8] 2009/08/30 15:51:16: Removing registration 9bce3cc2-e0e68f9c-e18edf11@71.249.202.7

[8] 2009/08/30 15:51:16: Removing registration e39a655c-c80b1bfa-331114bb@192.168.1.5

[8] 2009/08/30 15:51:16: Removing registration ac4a6b97-d5855f4d-6fde8e46@192.168.1.101

[8] 2009/08/30 15:51:16: Removing registration 6e6a2f02-8575837c-bc3e4d83@192.168.1.22

[8] 2009/08/30 15:51:16: Removing registration b7cea43a-868ba348-62fb3f31@192.168.2.2

[8] 2009/08/30 15:51:17: Removing registration e0c0d0f3-1d8235d9-d4be28c@71.249.202.7

[8] 2009/08/30 15:51:17: Removing registration b5388a1e-5cbb9efc-e76f7797@192.168.1.97

[8] 2009/08/30 15:51:17: Removing registration a1c13c04-b82de1ee-109ffaf1@24.189.101.131

[8] 2009/08/30 15:51:17: Removing registration c106de3d-4eec4e23-1e0f8da4@192.168.1.103

[8] 2009/08/30 15:51:18: Removing registration c05fa2cf-fd0ba5b5-1dec2f38@192.168.1.100

[8] 2009/08/30 15:51:18: Removing registration 33eb50ed-1df150f7-61ff1016@192.168.1.18

[8] 2009/08/30 15:51:18: Removing registration 71b56fb8-e157083e-35d9fca5@192.168.1.103

[8] 2009/08/30 15:51:18: Removing registration 7e5fae4e-c81db0d8-987d5dbd@192.168.1.2

[8] 2009/08/30 15:51:18: Removing registration fbb05865-732eb35b-4469696e@192.168.1.102

[8] 2009/08/30 15:51:18: Removing registration a64f0ef6-fdfbd498-ba4869d7@192.168.168.104

[8] 2009/08/30 15:51:18: Removing registration 5fd63078-268ac006-491590ad@10.10.0.108

[8] 2009/08/30 15:51:19: Removing registration f7e6f17b-ae73813d-841ab848@71.249.202.7

[8] 2009/08/30 15:51:19: Removing registration b643b053-2abc7ef5-e029570a@192.168.3.178

[8] 2009/08/30 15:51:19: Removing registration e5de8042-50121c90-fda9caf3@192.168.1.101

[8] 2009/08/30 15:51:19: Removing registration 30b95e0e-933559ec-671738f5@24.190.216.116

[8] 2009/08/30 15:51:19: Removing registration 6aecfad3-5de804c5-3dc7c880@192.168.15.100

[8] 2009/08/30 15:51:19: Removing registration 81d47f76-50cafa98-5d9282dd@192.168.1.101

[8] 2009/08/30 15:51:20: Removing registration 8ab51076-f6bb4f20-8319197f@192.168.7.147

[8] 2009/08/30 15:51:20: Removing registration 846fd3fe-c5a9854-13014957@192.168.168.105

[8] 2009/08/30 15:51:20: Removing registration ccb38ded-75a6a3cf-93e24a30@192.168.1.9

[8] 2009/08/30 15:51:20: Removing registration 422499a-4cceaf48-7992efad@192.168.7.79

[8] 2009/08/30 15:51:20: Removing registration 9f91521c-53799276-c37913cf@192.168.1.100

[5] 2009/08/30 15:51:20: Identify trunk (domain name match) 168

[8] 2009/08/30 15:51:20: Using outbound proxy sip:69.248.96.205:5061;transport=udp because UDP packet source did not match the via header

[8] 2009/08/30 15:51:20: Removing registration 1a7431b4-31343d22-c987bc2d@192.168.2.131

[8] 2009/08/30 15:51:20: Tagging request with existing tag

[7] 2009/08/30 15:51:20: Set packet length to 30

[6] 2009/08/30 15:51:20: Sending RTP for 75703eca-128220b8@192.168.1.104#743e66be91 to 192.168.1.104:16448

[8] 2009/08/30 15:51:20: Play audio_moh/noise.wav

[7] 2009/08/30 15:51:20: Set packet length to 30

[6] 2009/08/30 15:51:20: Send codec pcmu/8000

[6] 2009/08/30 15:51:21: Sending RTP for 75703eca-128220b8@192.168.1.104#743e66be91 to 69.248.96.205:16448

[8] 2009/08/30 15:51:21: Removing registration a78f4be2-3c9236e0-a10831ab@192.168.168.103

[8] 2009/08/30 15:51:21: Removing registration 3efafebb-a9541025-787ae3de@192.168.1.101

[8] 2009/08/30 15:51:21: Removing registration 3addab3b-4038176d-2d7f1a6e@71.249.202.7

[8] 2009/08/30 15:51:21: Removing registration 658fd809-675382ee-7b2ac347@192.168.8.2

[8] 2009/08/30 15:51:21: Removing registration 1ebcab15-c3b23c8b-b81647c@192.168.1.112

[8] 2009/08/30 15:51:21: Removing registration 92ec196f-6bab1701-a40486b0@24.189.101.131

[8] 2009/08/30 15:51:21: Removing registration e8560695-ef42939f-9a3e42fe@192.168.1.22

[8] 2009/08/30 15:51:21: Removing registration 8e94eb7-f18f1285-b88c520e@192.168.2.2

[8] 2009/08/30 15:51:21: Removing registration ad9ea8ce-9cc490ec-e286c353@192.168.1.104

[8] 2009/08/30 15:51:22: Removing registration 42de81e-548c3d9c-de1724ff@10.10.0.107

[7] 2009/08/30 15:51:22: Other Ports: 8

[7] 2009/08/30 15:51:22: Call Port: 74ba8daa@pbx#1444840570

[7] 2009/08/30 15:51:22: Call Port: 75703eca-128220b8@192.168.1.104#743e66be91

[7] 2009/08/30 15:51:22: Call Port: 8694f9ea@pbx#1209736123

[7] 2009/08/30 15:51:22: Call Port: 9723879b-654fb478@localhost#af51c45ece

[7] 2009/08/30 15:51:22: Call Port: 97922130@pbx#1505044189

[7] 2009/08/30 15:51:22: Call Port: D8916B48@sip10.siptrunk.com#ad806b5e6e

[7] 2009/08/30 15:51:22: Call Port: a4d2d529-40c61989@192.168.1.2#d7d50a349a

[7] 2009/08/30 15:51:22: Call Port: f95c0af0@pbx#1105414618

[8] 2009/08/30 15:51:22: DNS: Add dns_cname smtp.gmail.com gmail-smtp-msa.l.google.com (ttl=300)

[8] 2009/08/30 15:51:22: Removing registration a2679acd-d46619ab-c397cc4c@192.168.1.5

[8] 2009/08/30 15:51:22: Removing registration c5980538-1e01785e-c279495@192.168.1.10

[8] 2009/08/30 15:51:22: DNS: Add dns_aaaa gmail-smtp-msa.l.google.com (ttl=60)

[8] 2009/08/30 15:51:22: Removing registration e2a6385d-d8b940ff-3bce75d2@192.168.1.24

[8] 2009/08/30 15:51:22: Removing registration b70ee738-591eb9a-9d9b9a6f@192.168.1.45

[6] 2009/08/30 15:51:23: Sending RTP for 97922130@pbx#1505044189 to 169.132.188.44:24240

[8] 2009/08/30 15:51:23: Removing registration 399261ee-eac14620-6134e473@192.168.1.24

[6] 2009/08/30 15:51:23: Send codec=g729/8000 after answer

[7] 2009/08/30 15:51:23: 97922130@pbx#1505044189: RTP pass-through mode

[7] 2009/08/30 15:51:23: 75703eca-128220b8@192.168.1.104#743e66be91: RTP pass-through mode

[7] 2009/08/30 15:51:23: Different packet size (30 and 20), falling back to transcoding

[7] 2009/08/30 15:51:23: Different packet size (20 and 30), falling back to transcoding

[8] 2009/08/30 15:51:23: DNS: Add dns_a gmail-smtp-msa.l.google.com 74.125.91.109 (ttl=300)

[8] 2009/08/30 15:51:23: Removing registration 43c775a5-9e0f4e53-a388c780@192.168.1.125

[8] 2009/08/30 15:51:23: Removing registration e19cecdc-543413da-1e6d7ba9@192.168.1.100

[8] 2009/08/30 15:51:23: Removing registration 72cd44a3-a1d528ed-1c9cbf40@24.189.101.131

[8] 2009/08/30 15:51:23: Removing registration 7db26c30-19f6a5f6-64c90bc7@192.168.1.101

[8] 2009/08/30 15:51:24: Removing registration e47203ef-2a401d5d-2910b34c@192.168.168.105

[8] 2009/08/30 15:51:24: Removing registration 5fdcca92-575e4e48-d4ac4241@192.168.1.103

[Vodia PBX]

i have the same setting on all other trunks and it works fine, what do you suggest i do?

i want a solution thats going to work fine all over, i dont want based on certain phones to have to change anything

and also for some reason when i call from a linksys phone it works fine, but when calling from a polycom phone it doesnt work

 

Try locking all calls down (in the admin/ports section). This is the default for new installations anyway.

 

is it possible the polycom phones first try to use G729?

 

That will not make any difference. The PBX does not respect the codec preference of the UA.

[pbx support]

Try locking all calls down (in the admin/ports section). This is the default for new installations anyway.

 

 

 

That will not make any difference. The PBX does not respect the codec preference of the UA.

 

This is was resolved (after setting the lock codec under the ports page). The issue was net2phone was choosing g729, given an option of 711,729,etc.

BTW, in order to avoid transcoding, now we have set the trunk to do 711 only.

[pbxuser911]

all does work well now

i set it to only G711

what is intresting to note here, a linksys SPA962 phone worked no problem (no 1-way audio issues)

and a polycom IP601 did have the issue