priller
join:2000-10-20
Gainesville, VA
 ·voip.ms
·Callcentric
·Vonage
·callwithus
| Callcentric - "Pass Caller ID in SIP INVITE message"
I'm setting my CID number in the Remote-Party-ID of the SIP INVITE and CC is rejecting it to "SIP/2.0 403 User does not exist". The numbers I am passing are either DID's on my account or a verified number. »www.callcentric.com/new/#caller_id_in_invite
I am currently working with CC on this, but haven't come to a resolution. I was wondering if:
1) Anybody has been able to successfully use this feature with CC?
2) If so, could be do a packet capture and post how the Remote-Party-ID is formatted in your SIP INVITE message?
I'm using a SPA9000. The field is formatted as:
|
|
montano
join:2001-04-29
Central Cali | I have my SIP forwarding to 1777xxxxxxx@in.callcentric.com
Worth a shot perhaps ? |
|
priller
join:2000-10-20
Gainesville, VA
·voip.ms
·Callcentric
·Vonage
·callwithus
3 edits | reply to priller
If anybody's interested, here's what's happening.
With the desired outgoing CID number configured to be passed in the INVITE via the Remote-Party-ID, the same number also gets set in the FROM field ... instead of the CC 1777xxxxxxx number that would normally be there.
CC is responding with a "403 User does not exist" and the call is terminated.
Doing the same thing with VoIP.MS and Junction Networks, they both respond back with a "407 Proxy Authentication Required", not a 403. The INVITE is then resent with an additional "Proxy-Authorization" section in it (quick read of the RFC's say that is the expected behavior) and the call goes through.
EDIT: Also tried passing CID with Vitelity, they also reply with a 407 ... not a 403. Amazing how CC is right and everybody else is wrong! |
|
priller
join:2000-10-20
Gainesville, VA | Oh, well. CC just said there is nothing more they can do. I'll just sit back and wait until more people start reporting the same problem ... it's only day 2.  |
|
mbuugg
join:2008-04-04 | CallCentric prefix all incoming US CID with "1". I am sure the CID you verified with them is saved in the system as 17035551212. So now you know what to try. |
|
priller
join:2000-10-20
Gainesville, VA | Thx ... already checked ... tried it both ways. |
|
mbuugg
join:2008-04-04
| OK sorry that did not work. I did a test myself just now. When I used my cell number without the leading "1", the CID passed was my CC number. With the leading "1" the CID passed was my cell number. The finding is that if I put my cell number in the From header, I got the error "403 User does not exist". So that may depend on how SPA9000 works.
|
|
DogFace05
join:2005-12-09
Cary, NC
| reply to priller
This may or may not be the cause of your problem. The display name part of your Remote-Party-ID header is invalid in your example. It cannot contain spaces unless quoted. If you specify a display name that contains one or more spaces, or any of several other special characters, the whole name has to be enclosed in quotes, or else it invalidates the entire Remote-Party-ID header. Linksys should really have quoted it automatically and transparently, but they don't, so it's up to you to see to it that it gets done. You can have the quotes set for you by setting "Escape Display Name" to yes under the SIP tab. |
|
rmarynowski
join:1999-08-26
Tinley Park, IL | reply to priller
Not sure how to do it with the SPA9000, but it looks like people can do it with Asterisk/FreePBX:
»pbxinaflash.com/forum/showpost.p···tcount=4 |
|
priller
join:2000-10-20
Gainesville, VA
·voip.ms
·Callcentric
·Vonage
·callwithus
| reply to DogFace05
said by DogFace05  :This may or may not be the cause of your problem. The display name part of your Remote-Party-ID header is invalid in your example. ...... You can have the quotes set for you by setting "Escape Display Name" to yes under the SIP tab. Great tip, wasn't aware of that. However, that's not the cause of the problem.
With the SPA9000, I'm setting the outgoing CID number based on the extension. That's via the Contact List on the Line config. For example, Extension 101 should send CID number 17035551212 ... the Contact List syntax would be 17035551212:+101. What that's doing is presenting 17035551212 as the Remote-Party-ID and the local user-ID (FROM). CC rejects that because they still want to see their 1777xxxxxxx number as the FROM number in the INVITE. I see no way to preserve that.
As I noted above, CC rejects the call with a 403 and the call dies. Doing the same thing with Vitelity, VoIP.MS and Junction Networks, they all reject the initial INVITE with a 407 which the results in the SPA9000 resending the INVITE with the addition Proxy-Authorization and the call completes. I'm not smart enough to know if there is a right or wrong way, that's just what I'm observing.
CC position is that they are following RFC's, blah, blah. Since CC requires the CID number you send to be either a DID on your account or a verified number, it seems like they should be able to authenticate based on any of those and not just the 1777 number. They are attached to your account after all. I was surprised that sending a number (DID) that I own results in a "User does not exist". |
|
DogFace05
join:2005-12-09
Cary, NC | Try setting "Use Auth ID" to yes, and "Auth ID" to your CC user ID/URI ("1777xxxxxxx@callcentric.com"). |
|
priller
join:2000-10-20
Gainesville, VA
·voip.ms
·Callcentric
·Vonage
·callwithus
| said by DogFace05 :Try setting "Use Auth ID" to yes, and "Auth ID" to your CC user ID/URI ("1777xxxxxxx@callcentric.com"). Nope .. no change.
Using the Auth ID format: 1777xxxxxxx@callcentric.com , registration fails, CC doesn't like that.
Using the Auth ID format: 1777xxxxxxx , registers OK, but same problem. With CC you must have the Auth ID set or you can't register. |
|
PX Eliezer
Premium
join:2008-08-09
New Jersey | I'm 99 percent sure you did this already, but on the 1 percent chance that you didn't---
You did set the preferred CID on CallCentric's preferences section, on the dashboard? |
|
mbuugg
join:2008-04-04
| reply to priller
CC has their reason to do so because setting CID in From header or via Remote-Party-ID are defined in different RFC'es. VOIP providers may choose to support none/one of them but usually not both of them in one instance of a VOIP call. DF05 was trying to override the CID in the From header. If that did not work, try if you can find somewhere in the SPA9000 settings to disable CID being sent in the From header. |
|
priller
join:2000-10-20
Gainesville, VA
·voip.ms
·Callcentric
·Vonage
·callwithus
| reply to PX Eliezer
said by PX Eliezer :You did set the preferred CID on CallCentric's preferences section, on the dashboard? Well, that's what I'm trying to override and what the new feature should do. It should allow you to send CID number for any DID or verified number on your account. Even when sending the same number as the preferred CID, it doesn't work due to the FROM number not being the 1777. So, the INVITE is being rejected outright.
said by mbuugg : DF05 was trying to override the CID in the From header. If that did not work, try if you can find somewhere in the SPA9000 settings to disable CID being sent in the From header. Ya, been looking for that, but there's only so many knobs to turn and there doesn't seem to be a way to do it.
Oh, well. Thanks for the suggestions. If there's enough complaints, CC may change their behavior to match what the others are doing. |
|
