Jump to content

2.1.0 RC2 image available


Recommended Posts

  • Replies 70
  • Created
  • Last Reply

Top Posters In This Topic

Okay.

 

I still don't understand why G.729 would improve that situation... DTMF was not featured in this codec (it must be out of band then).

 

Are we talking about DTMF detection or DTMF transcoding here? Detection should be okay or better than previois versions, transcoding requires that the PBX falls back to RTP disassembly, which it should do automatically (there should be a log message about that).

Link to post
Share on other sites

Carrier supports Out Of Band DTMF for G729 but not for G711. Carrier require inband DTMF for G711.

 

Inband detection fails. Transcoding works.

 

 

Okay.

 

I still don't understand why G.729 would improve that situation... DTMF was not featured in this codec (it must be out of band then).

 

Are we talking about DTMF detection or DTMF transcoding here? Detection should be okay or better than previois versions, transcoding requires that the PBX falls back to RTP disassembly, which it should do automatically (there should be a log message about that).

Link to post
Share on other sites

Some more provisioning testing : the spa_1st.txt file has an extra http:// in - the {HTTP-URL} seems to include http://.

Also, once that's changed and the phone (an SPA942) is on the latest firmware, the phone requests the file and reboots, and I can see the pbx sends the config (with my extension etc. set), but after the reboot, the phone doesn't seem to have taken any of the settings.

 

Any ideas?

Link to post
Share on other sites
Hmm. Can you get a Wireshark trace and post me a private message where I can download it?

 

Okay, got the PCAP. Did you turn inband detection on on the PBX? See the admin settings at the bottom. See http://wiki.pbxnsip.com/index.php/Overall_...gs#SIP_Settings. My success in detecting inband depends on that flag.

Link to post
Share on other sites

That is really weired. I could hear the DTMF in the audio stream, it did not sound too bad.

 

Of course, jitter in the DTMF tones is very bad for the detection (that is why they invented out of band!), but I guess that does not seem to be the problem here.

 

[shrugging shoulders]

Link to post
Share on other sites
Well, I remember that was also a point that I simply did not understand. Seems there is a code that needs to be cracked with those phones.

 

Ok, I've got the linksys auto provisioning working, method is as below:

 

1. Edit spa_1st.txt to remove the extra http://

2. Edit spa_phone.txt and replace the all the {loop-count} tags with {loop-count 1} tags. In theory, changing the {loop-start} tags to {loop-start 1} should do it, but that doesn't seem to work.

3. Factory reset your phone - it will get the tftp server from your dhcp scope (assuming you've set it)

4. After 10-20 seconds it will get the spa_1st file by tftp and reboot.

5. After rebooting itself, the phone seems to need an extra reboot to get it to pull the config file, so reboot it (or cycle the power).

6. The phone will come back up, and after 10-20 seconds will pull the config via http, reboot and it will register with the PBX, assuming you set assigned the MAC to an extension.

 

Basically the default file tells the linksys to provision line_0, and it doesn't have a line_0. I'm still trying to work out why it needs the extra reboot after the initial TFTP, and why after provisioning it seems like I ca't dial out! Progress at least though.

 

Update:

 

Now have the provisioning working pretty much as it should. Add the line <Resync_Periodic ua="na"> 5</Resync_Periodic> to the SPA_1st.txt file and the phone will pull the http file correctly after the 1st reboot. I've had to edit a couple of bits in the spa_phone.txt as there's two tags which don't seem to work out of the box : {Dialplan SPA} and {TZ DST-SPA}. I'm guessing I need to set these somewhere in the pbx?

 

If anyone is interested, I'll post my files to the linksys part of the forum, as it includes strings for UK DST etc.

Link to post
Share on other sites

I know the DTMF is being sent because when we place a call outside of PBXnsIP the receiving end does detect the tones however tones to the IVR within PBXnSIP are undetected. Jitter is a non issue since this is on a LAN with minimal traffic.

 

 

 

That is really weired. I could hear the DTMF in the audio stream, it did not sound too bad.

 

Of course, jitter in the DTMF tones is very bad for the detection (that is why they invented out of band!), but I guess that does not seem to be the problem here.

 

[shrugging shoulders]

Link to post
Share on other sites
  • 2 weeks later...
  • 1 month later...
Well the Alert-Info header is controlled by a XML file (see below). Maybe it needs to be tweaked for the GS again. But most of the phones now understand this way of Alert-Info.

 

If you change the file, you can now re-load it through the web interface (admin/config?) to that you don't have to restart the service.

 

<?xml version="1.0"?>

<ringtones>

<tone name="custom1">

<vendor ua="Polycom.*" type="alert-info">Custom 1</vendor>

<vendor type="alert-info"><http://127.0.0.1/Bellcore-dr4></vendor>

</tone>

<tone name="custom2">

<vendor ua="Polycom.*" type="alert-info">Custom 2</vendor>

<vendor type="alert-info"><http://127.0.0.1/Bellcore-dr4></vendor>

</tone>

<tone name="custom3">

<vendor ua="Polycom.*" type="alert-info">Custom 3</vendor>

<vendor type="alert-info"><http://127.0.0.1/Bellcore-dr4></vendor>

</tone>

<tone name="custom4">

<vendor ua="Polycom.*" type="alert-info">Custom 4</vendor>

<vendor type="alert-info"><http://127.0.0.1/Bellcore-dr4></vendor>

</tone>

<tone name="internal" type="internal">

<vendor ua="Polycom.*" type="alert-info">Internal</vendor>

<vendor type="alert-info"><http://127.0.0.1/Bellcore-dr2></vendor>

</tone>

<tone name="external" type="external">

<vendor ua="Polycom.*" type="alert-info">External</vendor>

<vendor><http://127.0.0.1/Bellcore-dr3></vendor>

</tone>

<tone name="intercom" type="intercom">

<vendor ua="Polycom.*" type="alert-info">Auto Answer</vendor>

<vendor ua="Cisco-CP79.*">auto-answer=0</vendor>

<vendor type="call-info"><{from-uri}>;answer-after=0</vendor>

</tone>

</ringtones>

 

 

Just to bring this up again. I am trying to configure custom ring-tones for a customer when a call comes in on a hunt group. The Snom's BellCore's are not massively different. The SIP INVITE to the phone is sending through "Bellcore-dr4" (I selected Custom4 on the hunt group).

 

Is there anyway to change the Alert-Info headers that get sent to the phone, so for instance, I can select a custom WAV on a http server (http://10.0.0.1/my.wav)

Link to post
Share on other sites
  • 8 months later...
did somebody try this with the snom 320? could not find a template and does not seem so easy to me to configure.

 

i would love just to choose form the ringers in the phone "ringer 7"

 

thanx

Reco, I'm with Novus, a distributor of Snom and we are presently testing the pbxnsip in our lab in Tennessee. I will forward your question to Mark Orman our Senior Engineer and ask him to work on it next week. As the system is new to us, please give us a few days to get back to you.

Link to post
Share on other sites
  • 8 months later...
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.

Loading...



×
×
  • Create New...