You may want to try and capture some of that traffic with
wireshark/ethereal to see how it is coming to your system from Call
Manager.

 

If the traffic is coming from the IP address of the CM server, use the
IP address in your gateway definition on the sipXecs side.  If the
traffic is coming from a SIP domain, you should use the SIP domain in
the gateway definition and make sure that your sipXecs server has the
proper DNS records to resolve the domain name.

 

Mike

 

From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of arda savran
Sent: Wednesday, July 01, 2009 1:03 PM
To: sipx-users@list.sipfoundry.org
Subject: [sipx-users] SIP trunk between Cisco Callmanager 6 and SIPXECS

 

I built a SIP trunk between a CUCM6 and SIPXECS server in our lab.
Everything in CUCM6 regarding SIP trunk is set to non-secure standard.
I can make phone calls from the phones registered to the sipxecs server
to the phones registered to CUCM6 server.
However, when I try the the other way around, the sipxecs server sends a
407 Proxy authentication required message back to CUCM6 and the call
fails. I only hear a fast busy signal on the phone which is registered
to CUCM6.
 
On sipxecs, I set up the trunk as unmanaged gateway.
 
Any ideas on how to disable this 407 proxy authentication? Or any ideas
on how to configure CUCM to respond those requests from sipxecs
properly?
 
Thanks

 





________________________________

Windows Live(tm) SkyDrive(tm): Get 25 GB of free online storage. Get it
on your BlackBerry or iPhone.
<http://windowslive.com/online/skydrive?ocid=TXT_TAGLM_WL_SD_25GB_062009
> 

Checked by AVG - www.avg.com
Version: 8.5.375 / Virus Database: 270.13.1/2212 - Release Date:
07/01/09 05:53:00

_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to