Jump to content

Version 4 Codex problem ?


Happy
 Share

Recommended Posts

Could anyone explain to me the strange codex behaviour, that seems to take place since I upgraded my system to the latest version 4 ?

 

Log details below (don't find how to make attachements)

------------------

[4] 2010/10/25 08:13:08: Certificate for UTN-USERFirst-Hardware not available

[6] 2010/10/25 08:41:09: Sending RTP for 3c26f037f183-pmfuk042dnj0 to 192.168.1.111:60040, codec not set yet

[6] 2010/10/25 08:41:09: Codec pcmu/8000 is chosen for call id 3c26f037f183-pmfuk042dnj0

[6] 2010/10/25 08:45:37: Last message repeated 2 times

[6] 2010/10/25 08:45:37: Sending RTP for 3c26f1443a60-eo3jprew4xti to 192.168.1.111:51430, codec not set yet

[6] 2010/10/25 08:45:38: Codec pcmu/8000 is chosen for call id 3c26f1443a60-eo3jprew4xti

[6] 2010/10/25 08:45:42: Last message repeated 2 times

[6] 2010/10/25 08:45:42: Sending RTP for 3c26f1493088-l0rfsie8ywpl to 192.168.1.111:58142, codec not set yet

[6] 2010/10/25 08:45:43: Codec pcmu/8000 is chosen for call id 3c26f1493088-l0rfsie8ywpl

[6] 2010/10/25 09:01:52: Last message repeated 2 times

[6] 2010/10/25 09:01:52: Sending RTP for 3c2794bb2bf4-n6h6xmpisry6 to 192.168.1.23:55170, codec not set yet

[6] 2010/10/25 09:01:52: Codec pcmu/8000 is chosen for call id 3c2794bb2bf4-n6h6xmpisry6

[6] 2010/10/25 09:02:14: Last message repeated 2 times

[6] 2010/10/25 09:02:14: Sending RTP for 824d122fbf0cbdbd to 192.168.1.2:5238, codec not set yet

[3] 2010/10/25 09:02:14: Account 33 is not a Service Flag

[3] 2010/10/25 09:02:14: Hunt group 94 wants to add 6 members

[6] 2010/10/25 09:02:26: Codec pcmu/8000 is chosen for call id 6712bbf7@pbx

[6] 2010/10/25 09:02:26: Sending RTP for 6712bbf7@pbx to 192.168.1.21:55946, codec pcmu/8000

[6] 2010/10/25 09:02:26: Codec pcmu/8000 is chosen for call id 824d122fbf0cbdbd

[6] 2010/10/25 09:04:55: Sending RTP for 3d48f974f3b4f453 to 192.168.1.2:5240, codec not set yet

[3] 2010/10/25 09:04:56: Account 33 is not a Service Flag

[3] 2010/10/25 09:04:56: Hunt group 94 wants to add 6 members

[6] 2010/10/25 09:05:10: Codec pcmu/8000 is chosen for call id ca1a80bc@pbx

[6] 2010/10/25 09:05:10: Sending RTP for ca1a80bc@pbx to 192.168.1.21:49168, codec pcmu/8000

[6] 2010/10/25 09:05:10: Codec pcmu/8000 is chosen for call id 3d48f974f3b4f453

[6] 2010/10/25 09:06:24: Sending RTP for 05622ea9cd2c311c to 192.168.1.2:5242, codec not set yet

[3] 2010/10/25 09:06:24: Account 33 is not a Service Flag

[3] 2010/10/25 09:06:24: Hunt group 94 wants to add 6 members

[6] 2010/10/25 09:06:36: Codec pcmu/8000 is chosen for call id 1646ddb2@pbx

[6] 2010/10/25 09:06:36: Sending RTP for 1646ddb2@pbx to 192.168.1.23:57510, codec pcmu/8000

[6] 2010/10/25 09:06:36: Codec pcmu/8000 is chosen for call id 05622ea9cd2c311c

[6] 2010/10/25 09:07:53: Sending RTP for 52C428498BB2667E@192.168.1.1 to 192.168.1.1:7078, codec not set yet

[3] 2010/10/25 09:07:53: Hunt group 21 wants to add 6 members

[6] 2010/10/25 09:07:53: Codec pcmu/8000 is chosen for call id 52C428498BB2667E@192.168.1.1

[6] 2010/10/25 09:07:57: Sending RTP for 3c279627ef8b-w9hqobmv4z5o to 192.168.1.23:51182, codec not set yet

[6] 2010/10/25 09:07:57: Codec pcmu/8000 is chosen for call id 3c279627ef8b-w9hqobmv4z5o

[6] 2010/10/25 09:08:59: Last message repeated 2 times

[6] 2010/10/25 09:08:59: Sending RTP for 795D34D4A0751049@192.168.1.1 to 192.168.1.1:7078, codec not set yet

[3] 2010/10/25 09:08:59: Hunt group 21 wants to add 6 members

[6] 2010/10/25 09:08:59: Codec pcmu/8000 is chosen for call id 795D34D4A0751049@192.168.1.1

[6] 2010/10/25 09:09:21: Sending RTP for 3c2e50241a19-cgdthhcerdpi to 192.168.1.22:64732, codec not set yet

[6] 2010/10/25 09:09:21: Codec pcmu/8000 is chosen for call id 3c2e50241a19-cgdthhcerdpi

[6] 2010/10/25 09:13:08: Last message repeated 2 times

[4] 2010/10/25 09:13:08: HTTP client: Timeout on 173.166.77.221:443

[4] 2010/10/25 09:13:08: Certificate for UTN-USERFirst-Hardware not available

[6] 2010/10/25 09:14:47: Sending RTP for b53e7ab21fa8d6b0 to 192.168.1.2:5244, codec not set yet

[3] 2010/10/25 09:14:47: Account 33 is not a Service Flag

[3] 2010/10/25 09:14:47: Hunt group 94 wants to add 6 members

[6] 2010/10/25 09:15:02: Codec pcmu/8000 is chosen for call id b53e7ab21fa8d6b0

[3] 2010/10/25 09:15:11: Hunt group 95 wants to add 6 members

[6] 2010/10/25 09:15:17: Codec pcma/8000 is chosen for call id e15efdaf@pbx

[6] 2010/10/25 09:15:17: Sending RTP for e15efdaf@pbx to 192.168.1.26:49152, codec pcma/8000

[6] 2010/10/25 09:15:18: Different packet size (30 and 20), callid b53e7ab21fa8d6b0, falling back to transcoding

[6] 2010/10/25 09:15:18: Different packet size (20 and 30), callid e15efdaf@pbx, falling back to transcoding

[6] 2010/10/25 09:17:11: Received bindRequest for user pbx.praktijk.be\13

[6] 2010/10/25 09:17:18: Sending RTP for 3c279852a67d-jqmf892xc6fd to 192.168.1.23:57276, codec not set yet

 

--------------------------------------

Link to comment
Share on other sites

Could anyone explain to me the strange codex behaviour, that seems to take place since I upgraded my system to the latest version 4 ?

 

Log details below (don't find how to make attachements)

------------------

[4] 2010/10/25 08:13:08: Certificate for UTN-USERFirst-Hardware not available

[4] 2010/10/25 09:13:08: HTTP client: Timeout on 173.166.77.221:443

[4] 2010/10/25 09:13:08: Certificate for UTN-USERFirst-Hardware not available

[6] 2010/10/25 09:14:47: Sending RTP for b53e7ab21fa8d6b0 to 192.168.1.2:5244, codec not set yet

[3] 2010/10/25 09:14:47: Account 33 is not a Service Flag

[3] 2010/10/25 09:14:47: Hunt group 94 wants to add 6 members

[6] 2010/10/25 09:15:02: Codec pcmu/8000 is chosen for call id b53e7ab21fa8d6b0

[3] 2010/10/25 09:15:11: Hunt group 95 wants to add 6 members

[6] 2010/10/25 09:15:17: Codec pcma/8000 is chosen for call id e15efdaf@pbx

[6] 2010/10/25 09:15:17: Sending RTP for e15efdaf@pbx to 192.168.1.26:49152, codec pcma/8000

[6] 2010/10/25 09:15:18: Different packet size (30 and 20), callid b53e7ab21fa8d6b0, falling back to transcoding

[6] 2010/10/25 09:15:18: Different packet size (20 and 30), callid e15efdaf@pbx, falling back to transcoding

[6] 2010/10/25 09:17:11: Received bindRequest for user pbx.praktijk.be\13

[6] 2010/10/25 09:17:18: Sending RTP for 3c279852a67d-jqmf892xc6fd to 192.168.1.23:57276, codec not set yet

 

--------------------------------------

 

If you are talking about "....codec not set yet", that's ok. It is not a problem. But if you are taking about the "...falling back to transcoding", then there is some phone or trunk provider doing 30ms packet instead of default 20ms. You need to find out who is doing 30ms and change it to do 20ms.

Link to comment
Share on other sites

If you are talking about "....codec not set yet", that's ok. It is not a problem. But if you are taking about the "...falling back to transcoding", then there is some phone or trunk provider doing 30ms packet instead of default 20ms. You need to find out who is doing 30ms and change it to do 20ms.

I was concerned about both.

If I understand you correcly, I have to ask the voip provider to change teh 30ms packet to 20ms. There is no way to adapt pbxnsip to the provider's settings ?

Link to comment
Share on other sites

I was concerned about both.

If I understand you correcly, I have to ask the voip provider to change teh 30ms packet to 20ms. There is no way to adapt pbxnsip to the provider's settings ?

 

Yes that could be a source for trouble. There are two settings that you can check in admin/ports: The packet size (set it to 30 ms) and the question if the PBX should always send the packet size (set it to yes).

Link to comment
Share on other sites

Is TLS not a 'standard' feature in a Snom phone - Pbxnsip environment ? Is there a way to track this problem down ?

 

Yes, but you need to establish trust relationships (this is a standard TLS problem). In snom ONE, snom trusts snom (kind of makes sense), but it by default does not trust anything else. If you are using other providers for certificates, you need to import the right Root CA.

Link to comment
Share on other sites

Yes that could be a source for trouble. There are two settings that you can check in admin/ports: The packet size (set it to 30 ms) and the question if the PBX should always send the packet size (set it to yes).

Change the admin/ports packet size in Pbxnsip would influence connections to all trunks and phones, I suppose.

Found a phone : a sipura device with a non-standard 30millisec setting!

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...