hmcap
-
Posts
13 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by hmcap
-
-
Most service providers use other service providers to terminate their traffic, and the routing can be really unpredictable. So they might not have it in their hands on how exactly the caller-ID is being presented. Especially if they dont use SBC (instead use SIP proxy model), it is practically impossible to keep this 100 % under control.
Keep the 20 secs for some time until the dust settles. This is something that should not hurt, except for generating higher traffic. Later you can try to slow it down or seek other ways to keep the connection alive (e.g. put the trunk on a public IP address).
OK. Thanks. I wait and see what happens. Remains one thing; yes or no upgrading to the latest version?
-
I would just try to keep the trunk alive by forcing the PBX to re-register every 20 seconds. From what I saw about the provider, they expect the PBX to keep the connection alive.
I don't get it. The connection (our DID mapped to voipcheap > which is a trunk in pbxnsip) is answering calls again. I did set the keep-alive-time to 20 seconds. So, would it be safe to upgrade to 4.2.1.4025? I still have some issues with the caller-id.
The trunks voipcheap & voipbuster are showing the ANI I put in the trunk and using RFC3325 (P-asserted-ID) and it shows the ANI I wanted to show. But another trunk from the same company with the same settings is showing 'Blocked' or 'Unknown"
-
Well, there is no INVITE coming in at all... So it must be something with the firewall I guess. Firewalls and NAT continue to be a pain in the neck when it comes to SIP, sorry for that.
Also, it seems that your service provider does not provide the convenience of a session border controller to keep the connection alive or support something like outbound (which automatically set up STUN as a refresh method). A easy way to fix this is to set the "Keepalive Time" in the trunk to 20 seconds.
I checked the firewall; all sip traffic is passed. I only have problems with voipcheap & voipbuster trunks. Our trunk from callvoip is working (set to only inbound). I read that version 4.2.1.4025 that 'A false 200 OK (Trunk registration issue) occurred as a result of a glitch in the DNS interaction.' has been solved. I downgraded to x.x.x.3981 (mac OS X) because of no connection.
Do I have to upgrade again? And how do you check whether the trunk registration is real?
-
[8] 2011/07/06 18:04:04: DNS: Add SRV _sips._tcp.sip.voipcheap.com (ttl=60)
[4] 2011/07/06 18:04:04: Could not find packet with number 261
[5] 2011/07/06 18:04:05: SIP Rx udp:ip:5060:
REGISTER sip:server SIP/2.0
Via: SIP/2.0/UDP ip:5060;branch=z9hG4bK2b9c042c28709b9362bd516c5663fae0;rport
From: "name" <sip:371@ip>;tag=1400395483
To: "name" <sip:371@ip>
Call-ID: 2611753284@ip4
CSeq: 5856 REGISTER
Contact: <sip:371@ip:5060>
Max-Forwards: 70
User-Agent: A580 IP022230000000
Expires: 3600
Allow: INVITE, ACK, CANCEL, BYE, OPTIONS, INFO, REFER, SUBSCRIBE, NOTIFY
Content-Length: 0
[5] 2011/07/06 18:04:05: SIP Tx udp:ip4:5060:
SIP/2.0 200 Ok
Via: SIP/2.0/UDP 192.168.178.4:5060;branch=z9hG4bK2b9c042c28709b9362bd516c5663fae0;rport=5060
From: "name" <sip:371@ip>;tag=1400395483
To: "name" <sip:371@ip>;tag=3942b0d123
Call-ID: 2611753284@ip
CSeq: 5856 REGISTER
Contact: <sip:371@ip:5060>;expires=359
Content-Length: 0
[5] 2011/07/06 18:04:25: SIP Rx tls:ip:3807:
REGISTER sip:localhost SIP/2.0
Via: SIP/2.0/TLS ip:3807;branch=z9hG4bK-uls8ndemvpej;rport
From: "name" <sip:300@localhost>;tag=1x5hfgqrvu
To: "namen" <sip:300@localhost>
Call-ID: 3770263cf216-q3qcpm0hwu0x
CSeq: 45861 REGISTER
Max-Forwards: 70
Contact: <sip:300@IP:3807;transport=tls;line=6qt0xsxs>;reg-id=1;q=1.0;+sip.instance="<urn:uuid:9946764b-eb87-4c38-a93b-a00c98fa2a33>"
User-Agent: snom870/8.4.31
Allow-Events: dialog
X-Real-IP:
Supported: path, gruu
Proxy-Require: buttons
Expires: 3600
Content-Length: 0
-
I'll post my question here and also in 'general', but I pretty desperate and don't know where to start. It happens after upgrading to 4.2.1.4025. First I had some problems with the caller-ID and now all my inbound trunks are not working. I've a DID via DIDWW, which is mapped to a voipcheap-trunk with a failover to a voipbuster-trunk. Since two days, it is not possible anymore to call our office. A long silence is heard. I than down=graded to x.x.x.3981 and it looks like the snom one was working again. Just for a few minutes and the office was not reacheable again. How to solve this? I don't know where to start looking, but it has to work.
Regards,
Harry
-
I'll post my question here and also in 'general', but I pretty desperate and don't know where to start. It happens after upgrading to 4.2.1.4025. First I had some problems with the caller-ID and now all my inbound trunks are not working. I've a DID via DIDWW, which is mapped to a voipcheap-trunk with a failover to a voipbuster-trunk. Since two days, it is not possible anymore to call our office. A long silence is heard. I than down=graded to x.x.x.3981 and it looks like the snom one was working again. Just for a few minutes and the office was not reacheable again. How to solve this? I don't know where to start looking, but it has to work.
Regards,
Harry
-
BTW, you did not mention whether you tried "No indication" option. Some carriers do not like any of these secondary headers. They like only "From" header.
I think the easiest way to solve this issue is to know what will make intervoip display the proper caller-id . Only intervoip folks can tell you what makes them happy.
Sorry, didn't mention that, but tried it also. No results. I also posted a support request to the intervoip-desk. I supllied them with date, time, codec, called number etc. and they checked the settings. What they say is that they don't block caller-id's, ani's etc.
Now I tried RFC3325 custom, but no results either
-
Hi all,
I'm using four different trunks and three of them belongs to the Betamax corp; voipbuster, voipcheap and intervoip. The first two are already 2-3 years in use and having no problems with them. Since version 4.x I'm able to send the caller-ID, which is set in the ANI of the trunk. This week I'm also using intervoip.com because of the low rates for calling cell phones in the Netherlands. Setting up was easy and within minutes I could use this trunk. I used the same settings as their fellow-products from Betamax, but didn't succeed in showing the caller-ID. Which setting I used, when calling a cell phone number via the intervoip-trunk, 'unknown' or 'blocked number' appears in the display of the cell phone. I tried:
1. RFC3325 (P-asserted-identity)
2. RFC3325 (P-preferred-identity)
3. Remote party ID
4. RFC332, but don't hide
5. RFC 3325, custom (haven't tried this one yet)
The dialplan is tells the system when an extension calls a cell-phone number, eq 06xxxxxxxx, then choose trunk intervoip with number 06xxxxxx. Else, use trunk A for Europe or B for outside Europe.
How do I deal with this and where should I look?
Regards,
Harry
-
If you were running pbxnsip version, then the upgrade should be done using a pbxnsip version.
The snomONE license keys will not work on pbxnsip version.
If you do a fresh install with the snomONE dmg file and then apply the "free" license (before making any other changes) from Admin->License page, it should work.
That's exactly what I did. Took the update from the pbxnsip-website. Run terminal and followed the instructions on the snomOne site. I also removed my old license > clicked on save. Chose evaluation > click save again. Looked at the results in the status-tab but no change in license; meaning 'no license'.
In case of the snomOne dmg-file:
Removed all the files and took the snomOne-dmg and run the installation-script. Opened Safari 5.05 (and Firefox 4.01), went to localhost, logged in as admin, went to admin > settings > license > clicked free > saved. Went to status; ;license : snomone free > version 4.2.0.3958.
Logged out. Downloaded the snomOne update (4.2.0.3981) > install via terminal. I open the browser and see a warning sign as soon as I open localhost. Goto license and see that a unknown license string is filled in (in option 2) Removed the string > click save > choose for free version> click save. Go to status and the license type, which was snomOne free in version 4.2.0.3958 has gone and turned into 'no license'.
If I had not any problems with my email-settings and some problems with our Snom 821, I wouldn't go through all this trouble to update. But apperently the email and snom 821 problems should be solved with the latest version. Hence my efforts to update.
regards,
harry
-
Hi all,
A few weeks ago I posted a topic regarding the licensing of pbxsnip versus snomone. I'm still confused and rather desperate when it come this subject. I'm running the original pbxnsip version 4.2.03958, licensed up to 10 extensions. Works great, but after upgrading to my current version things like email doesn't work anymore. Before that I used the smtp-server from our cable company and it just works. In version 4.2.0.3958, this doesn't function anymore.
I've read the different topics in the forum; using Gmail in version 4.2.0.3958, how to add certificates etc. I tried all, and tried also to update to the latest version 4.2.0.3981; did by cmd-line; works perfect. But, when I login as admin the first thing I see is the current version is not licensed. That's correct, the license period is over and since a free snomOne is on the market and pbxnsip is off the market, it doesn't make sense to extend our pbxnsip-license.
So, I red the different fora again and came along this advice; go to admin, > settings > license, remove the old license, click on evaluation version > click save. And this should do it.
But when I click on status>general I still see 'no license' despite the fact I tried it a few times, but it looks like whenever I remove the old license and click save; it returns a license string back. It just doesn't accept the free-mode.
Does anyone have any tips or advice or how to handle this? I also tried to erase the folder containing pbxnsip, do a 'clean' install with the .dmg-file from the snomone website. What you got is version 4.2.0.3958 so the manual update to 4.2.0.3981 by cmd-line and got back where I started; an updated version 4.2.0.3981 but not able to register either the phones or trunks.
Where should I look? Are there any hidden files? Any advice welcome.
Regards,
Current config:
Mac Mini intel core 2
Mac OS 10.6
pbxnsip 4.2.0.3958
Harry
-
sound like your software maintenance expired. downgrade back the old version.
Unfortunately you're right. I had to downgrade and the system works again. But communication about doing these updates from either pbxnsip(now Snom) and Snom are transparant enough.
Thanks,
harry
-
Hi all,
I'm confused and rather a bit in distress. I ran a pbxnsip (mac version 4.2.3958) and just 50 minutes ago I downloaded the update (4.2.3981), used the command-line to update and saved the current config as backup.
Restarted, everything worked fine, noticed the new version, checked all the tabs in admin-mode and saw to my suprise that I was running a no-licensed version. With that, I noticed that the trunks are registring and also the accounts are not registring.
I looked-up the license string pbxnsip gave me when I purchased the pbxnsip, copy-paste, but still no go!
What went wrong, I can't downgrade, since the link to the version 4.2.3958 has been closed and being forwarded to snomOne.
Any advice welcome!! Hopefully before monday, when the week starts again.
best regards,
Harry
having trouble with remote party ID (RFC3325)
in Trunk Setup
Posted
This is what I see:
REGISTER sip:sip.intervoip.com SIP/2.0
Via: SIP/2.0/UDP 192.168.178.2:5060;branch=z9hG4bK-228b437f70d3de59a798b4f6154e2b06;rport
From: "useraccount" <sip:useraccount@sip.intervoip.com>;tag=1837272285
To: "useraccount" <sip:useraccount@sip.intervoip.com>
Call-ID: tm4no6yf@pbx
CSeq: 52555 REGISTER
Max-Forwards: 70
Contact: <sip:useraccount@192.168.178.2:5060;transport=udp;line=c9f0f895>;+sip.instance="<urn:uuid:9bee35c9-5835-4cf5-83d7-1e85c72840b5>"
User-Agent: pbxnsip-PBX/2011-4.2.0.3981
Supported: outbound
Authorization: Digest realm="sip.intervoip.com",nonce="543939485",response="f0e61f67629d2ce15b84a1a29c987adf",username="useraccount",uri="sip:sip.intervoip.com",algorithm=MD5
Expires: 3600
Content-Length: 0
Where can I see the RFC-header?