[cisco-voip] Sip Device help

[Ryan Ratliff]

You add a DN the same as any other phone, on the left side of the  
phone config page.   It's certainly possible that the phone is trying  
to register a DN that isn't assigned to it in CM.  I wouldn't expect  
that to cause it to lose registration after a few minutes but rather  
to never get registered.

Make sure you have the SIP trace options and Keepalives turned on in  
detailed ccm traces and take a look at the SIP messaging to the  
phone.   I know the keepalive mechanism is very similar to  
registration so maybe the keepalive is missing the DN?

You can change the SIP keepalive timer in the SIP Profile, "Timer  
Keep Alive Expires".

-Ryan

On Jan 11, 2008, at 10:04 AM, Mike Glass wrote:

Can I actually Change the SIP Keepalive on CM

Right now I have it configured as a Third Party Sip Device

Here Is the message from callmanager

ÌM_CALLMANAGER-CALLMANAGER-3-DeviceUnregistered: Device unregistered.  
Device name.:SEP0020F7500752 Device IP address.:172.18.64.22  
Protocol.:SIP Device type. [Optional]:336 Device description  
[Optional].:Shop Intercom Reason Code [Optional].:13 Cluster  
ID:StandAloneCluster Node ID:LCC-CCB-CCM1


Reason code 13 is  DirectoryNumberMismatch, how and where do I assign  
it a DN.
I have a user created as the same name as the DN associated with the  
phone.
The phone is associated with the user in Controlled devices. I have  
the user setup in cyberdata as both the SIP UserID: and Authenticate  
ID: and have the password entered for that user, SIP Registration  
Turned on.








 >>> Ryan Ratliff <rratliff at cisco.com> 1/11/2008 7:45 AM >>>
They probably aren't sending keepalives correctly. I've run into this  
with another 3rd party SIP developer. I believe the default SIP  
keepalive is like 2 minutes or something.

-Ryan

On Jan 10, 2008, at 5:22 PM, Mike Glass wrote:

I am running 6.1. I have added as a 3rd party device and it registers  
for about 5 minutes then un-registers. I have tried it as a sip trunk  
also. CyberData is the worst company to get anything out of, even if  
Cisco is a partner, nobody seems to know. I guess its time for a refund.
Anybody know of a good intercom device to plug into an existing amp  
and will work with a Cisco ip system?

 >>> Ryan Ratliff <rratliff at cisco.com> 1/9/2008 11:42 AM >>>
Those look like SIP client options. What version of CallManager are  
you using with this device? If it's 5.x or 6.x have you tried adding  
it as a 3rd party SIP device?

-Ryan

On Jan 9, 2008, at 1:33 PM, Mike Glass wrote:

these are the only parameters on the Setup for the device.
SIP Server : *
Remote SIP Port: 5060
Local SIP Port: 5060
SIP User ID: ?
Authenticate ID: ?
Authenticate Password: ?
SIP Registration: Yes No ?
Unregister on Reboot: Yes No *
Register Expiration (minutes): *

 >>> Matthew Saskin <matt at saskin.net> 1/9/2008 11:03 AM >>>
That's basically all you need to get calls to route to it provided that
your route pattern is in a partition that is reachable from the calling
device.

Beyond that, you need to make sure the other device is configured
properly, that you're sending it the proper number of digits (if it
expects any), etc....

Mike Glass wrote:
 > I have a Cyberdata VoIP Paging Zone Controller 4-Port Audio Out from
 > http://www.cyberdata.net/products/voip/voip-zonecontroller.html
 >
 > I have created a sip trunk with using the ip of the device, and  
created
 > a route pattern pointing to the Sip Trunk. What else do I need to
 > configure to use this device as a intercom device.
 >
 > Thanks
 >
 >
 >  
------------------------------------------------------------------------
 >
 > _______________________________________________
 > cisco-voip mailing list
 > cisco-voip at puck.nether.net
 > https://puck.nether.net/mailman/listinfo/cisco-voip

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip



-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://puck.nether.net/pipermail/cisco-voip/attachments/20080111/c4a51b0f/attachment.html