| Jonathan Charles 2007-06-04, 1:12 pm |
| Actually, on the PRI debugs, I am not seeing any calling name info...
Jonathan
On 6/4/07, Vince Loschiavo <VLoschiavo@data-corporation.com> wrote:
> Not necessarily.
>
> Sometimes this is call manager not accepting the Caller-ID names.
>
> ________________________________________
____________________
> Vincent Loschiavo
> Senior Consultant
> Datacorp
> 18503 Pines Blvd, Suite 212, Pembroke Pines, FL, 33029
> "Cisco Advanced Unified Communications Partner"
> Cell Phone: 786-282-1164
> Office Phone: 305-594-6933
> ________________________________________
____________________
> -----Original Message-----
> From: cisco-voip-bounces@puck.nether.net
> [mailto:cisco-voip-bounces@puck.nether.net] On Behalf Of Jonathan
> Charles
> Sent: Wednesday, May 30, 2007 4:57 PM
> To: ciscovoip
> Subject: [cisco-voip] ISDN PRI - Message not compatible with call
> state...
>
> Getting a message on PRI debugs, just wondering if it is something to
> be concerned about :
>
> Cause i = 0x80E56E - Message not compatible with call state
>
> Cisco's website says this for this code:
>
> The remote equipment receives an expected message that does not
> correspond to the current state of the connection.
>
> This issue occurs due to a D-channel error.
>
>
> Is this bad???
>
> the call connects...
>
>
>
> Jonathan
> ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
|